CVE-2026-89741

published 11 Sep 2026 · updated 20 Nov 2026

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

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8b998c171ed875e402e1fd1c5cd619e4ca05e9c1, Kernel 5.15.221, Kernel 5.5 and 14 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=e5c8e62ae551e0ad2e15412aa0c57c2856d59677 <8b998c171ed875e402e1fd1c5cd619e4ca05e9c1, >=5.15.186 <5.15.221, >=5.4.295 <5.5, >=6.1.142 <6.1.188, >=6.12.35 <6.12.109, >=6.15.4 <6.16, >=6.6.95 <6.6.157, >=8b451a9a46f2bfc510e6d5c2492df91647586184 <3de14b4f681a1b3c6d375d98d9d37a55ebb85349, >=ae7b143e05b36fc69d6571751855946cc45064c6 <2ac009a65d2385e9f0799eaf9d9694a29153a161, >=b6be1f5633eae200af2527e9eeb7f51be5739b0f <8027f82c0f5474ed72448e160ee9778051fa1f49, =4451412739ed33a49b34624299394ee575116d0c, =6.16, =ee141706e701356dda41c6fed9ee18bf427c28e3, >=2429bb9fad88c8fa84c4956b0a21cf5afe5e92b7 <712ca1cf756de2557a116e0df55791bac0c9f99e, >=2a934fdb01db6458288fc9386d3d8ceba6dd551a <aad08b5f67d2a8116e1a00bce2611c1513b10bce, >=2a934fdb01db6458288fc9386d3d8ceba6dd551a <ce792b94e03882108019ba996c1a7c4d4e09be2c, >=2a934fdb01db6458288fc9386d3d8ceba6dd551a <e7600f5cee5de14065f950807931d6e6d40fb2d7, >=5.10.239 <5.10.2708b998c171ed875e402e1fd1c5cd619e4ca05e9c1, 5.15.221, 5.5, 6.1.188, 6.12.109, 6.16, 6.6.157, 3de14b4f681a1b3c6d375d98d9d37a55ebb85349, 2ac009a65d2385e9f0799eaf9d9694a29153a161, 8027f82c0f5474ed72448e160ee9778051fa1f49, 712ca1cf756de2557a116e0df55791bac0c9f99e, aad08b5f67d2a8116e1a00bce2611c1513b10bce, ce792b94e03882108019ba996c1a7c4d4e09be2c, e7600f5cee5de14065f950807931d6e6d40fb2d7, 5.10.270
linux-kernel: Kernel>=5.15.186 <5.15.221, >=5.4.295 <5.5, >=6.1.142 <6.1.188, >=6.12.35 <6.12.109, >=6.15.4 <6.16, >=6.16.0 <6.18.50, >=6.19.0 <7.2.4, >=6.6.95 <6.6.157, >=5.10.239 <5.10.2705.15.221, 5.5, 6.1.188, 6.12.109, 6.16, 6.18.50, 7.2.4, 6.6.157, 5.10.270

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-89741 severity on Zeptric[![CVE-2026-89741](https://zeptric.io/badge/cve/CVE-2026-89741.svg)](https://zeptric.io/cve/CVE-2026-89741)