Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89741, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected e5c8e62ae551e0ad2e15412aa0c57c2856d59677 – < 8b998c171ed875e402e1fd1c5cd619e4ca05e9c1
    • affected 8b451a9a46f2bfc510e6d5c2492df91647586184 – < 3de14b4f681a1b3c6d375d98d9d37a55ebb85349
    • affected b6be1f5633eae200af2527e9eeb7f51be5739b0f – < 8027f82c0f5474ed72448e160ee9778051fa1f49
    • affected ae7b143e05b36fc69d6571751855946cc45064c6 – < 2ac009a65d2385e9f0799eaf9d9694a29153a161
    • affected 2429bb9fad88c8fa84c4956b0a21cf5afe5e92b7 – < 712ca1cf756de2557a116e0df55791bac0c9f99e
    • affected 2a934fdb01db6458288fc9386d3d8ceba6dd551a – < aad08b5f67d2a8116e1a00bce2611c1513b10bce
    • affected 2a934fdb01db6458288fc9386d3d8ceba6dd551a – < ce792b94e03882108019ba996c1a7c4d4e09be2c
    • affected 2a934fdb01db6458288fc9386d3d8ceba6dd551a – < e7600f5cee5de14065f950807931d6e6d40fb2d7
    • affected ee141706e701356dda41c6fed9ee18bf427c28e3
    • affected 4451412739ed33a49b34624299394ee575116d0c
    • affected 5.10.239 – < 5.10.270
    • affected 5.15.186 – < 5.15.221
    • affected 6.1.142 – < 6.1.188
    • affected 6.6.95 – < 6.6.157
    • affected 6.12.35 – < 6.12.109
    • affected 5.4.295 – < 5.5
    • affected 6.15.4 – < 6.16
  • Linux · Linux

    • affected 6.16
    • unaffected < 6.16
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89741 badge
[![CVE-2026-89741](https://cveledger.app/badge/CVE-2026-89741.svg)](https://cveledger.app/cve/CVE-2026-89741)

Record last updated .