CVE-2026-89741

Revert "media: v4l2-dev: fix error handling in __video_register_device()"

State
Published
Severity
7.8 High
Published
Sep 11, 2026
Updated
Oct 19, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

Revert "media: v4l2-dev: fix error handling in __video_register_device()"

This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.

The intentions of that patch were good, but it doesn't work.

The idea is that if device_register fails, you have to do a put_device to let the ref counter release resources.

However, the V4L2 API says that if video_register_device() fails, then you have to call video_device_release(), which kfree()s the video_device struct.

But the put_device() will already have freed the struct, so you end up in a double-free scenario.

There is not really a good way of fixing this without breaking video_register_device() into two parts, one that initializes everything, and one that does the actual device_register, and then converting all V4L2 drivers to this new model.

That is a massive job, and it is very unlikely that device_register will fail.

So rather than ending up in a double-free scenario, just revert this patch, and in that case we'll have a small memory leak. Which is a lot more robust.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • e5c8e62ae551e0ad2e15412aa0c57c2856d59677 to before 8b998c171ed875e402e1fd1c5cd619e4ca05e9c1Affected
  • 8b451a9a46f2bfc510e6d5c2492df91647586184 to before 3de14b4f681a1b3c6d375d98d9d37a55ebb85349Affected
  • b6be1f5633eae200af2527e9eeb7f51be5739b0f to before 8027f82c0f5474ed72448e160ee9778051fa1f49Affected
  • ae7b143e05b36fc69d6571751855946cc45064c6 to before 2ac009a65d2385e9f0799eaf9d9694a29153a161Affected
  • 2429bb9fad88c8fa84c4956b0a21cf5afe5e92b7 to before 712ca1cf756de2557a116e0df55791bac0c9f99eAffected
  • 2a934fdb01db6458288fc9386d3d8ceba6dd551a to before aad08b5f67d2a8116e1a00bce2611c1513b10bceAffected
  • 2a934fdb01db6458288fc9386d3d8ceba6dd551a to before ce792b94e03882108019ba996c1a7c4d4e09be2cAffected
  • 2a934fdb01db6458288fc9386d3d8ceba6dd551a to before e7600f5cee5de14065f950807931d6e6d40fb2d7Affected
  • ee141706e701356dda41c6fed9ee18bf427c28e3Affected
  • 4451412739ed33a49b34624299394ee575116d0cAffected
  • 5.10.239 to before 5.10.270Affected
  • 5.15.186 to before 5.15.221Affected
  • 6.1.142 to before 6.1.188Affected
  • 6.6.95 to before 6.6.157Affected
  • 6.12.35 to before 6.12.109Affected
  • 5.4.295 to before 5.5Affected
  • 6.15.4 to before 6.16Affected
LinuxLinux
  • 6.16Affected
  • before 6.16Not affected
  • 5.10.270 through 5.10.*Not affected
  • 5.15.221 through 5.15.*Not affected
  • 6.1.188 through 6.1.*Not affected
  • 6.6.157 through 6.6.*Not affected
  • 6.12.109 through 6.12.*Not affected
  • 6.18.50 through 6.18.*Not affected
  • 7.2.4 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.