Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2ac009a65d2385e9f0799eaf9d9694a29153a161, 3de14b4f681a1b3c6d375d98d9d37a55ebb85349, 5.10.270; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2ac009a65d2385e9f0799eaf9d9694a29153a161, 3de14b4f681a1b3c6d375d98d9d37a55ebb85349, 5.10.270; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-89741

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • ee141706e701356dda41c6fed9ee18bf427c28e3, 4451412739ed33a49b34624299394ee575116d0c, 6.16affected
    • e5c8e62ae551e0ad2e15412aa0c57c2856d59677 and later · before 8b998c171ed875e402e1fd1c5cd619e4ca05e9c1affected · git
    • 8b451a9a46f2bfc510e6d5c2492df91647586184 and later · before 3de14b4f681a1b3c6d375d98d9d37a55ebb85349affected · git
    • b6be1f5633eae200af2527e9eeb7f51be5739b0f and later · before 8027f82c0f5474ed72448e160ee9778051fa1f49affected · git
    • ae7b143e05b36fc69d6571751855946cc45064c6 and later · before 2ac009a65d2385e9f0799eaf9d9694a29153a161affected · git
    • 2429bb9fad88c8fa84c4956b0a21cf5afe5e92b7 and later · before 712ca1cf756de2557a116e0df55791bac0c9f99eaffected · git
    • 2a934fdb01db6458288fc9386d3d8ceba6dd551a and later · before aad08b5f67d2a8116e1a00bce2611c1513b10bceaffected · git
    • 2a934fdb01db6458288fc9386d3d8ceba6dd551a and later · before ce792b94e03882108019ba996c1a7c4d4e09be2caffected · git
    • 2a934fdb01db6458288fc9386d3d8ceba6dd551a and later · before e7600f5cee5de14065f950807931d6e6d40fb2d7affected · git
    • 5.10.239 and later · before 5.10.270affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-89739Sep 11, 2026 · usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition
    0Monitor
  • ← EarlierCVE-2026-89740Sep 11, 2026 · serial: imx: serialize imx_uart_ports[] lifetime
    0Monitor
  • Later →CVE-2026-89742Sep 11, 2026 · rapidio: mport_cdev: fix use-after-free in dma_req_free()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2ac009a65d2385e9f0799eaf9d9694a29153a161Vendor (CNA)
Linux Linux3de14b4f681a1b3c6d375d98d9d37a55ebb85349Vendor (CNA)
Linux Linux5.10.270Vendor (CNA)
Linux Linux5.15.221Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux6.1.188Vendor (CNA)
Linux Linux6.12.109Vendor (CNA)
Linux Linux6.16Vendor (CNA)
Linux Linux6.6.157Vendor (CNA)
Linux Linux712ca1cf756de2557a116e0df55791bac0c9f99eVendor (CNA)
Linux Linux8027f82c0f5474ed72448e160ee9778051fa1f49Vendor (CNA)
Linux Linux8b998c171ed875e402e1fd1c5cd619e4ca05e9c1Vendor (CNA)
Linux Linuxaad08b5f67d2a8116e1a00bce2611c1513b10bceVendor (CNA)
Linux Linuxce792b94e03882108019ba996c1a7c4d4e09be2cVendor (CNA)
Linux Linuxe7600f5cee5de14065f950807931d6e6d40fb2d7Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records