Skip to main content
VulnerabilityPublished Updated

CVE-2026-68205: Linux kernel · media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f35e85a9d919d7954d9a7752e4644c0b403ad025 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:18 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f35e85a9d919d7954d9a7752e4644c0b403ad025, cf9732fd6c4f2f803ccfc46d89489b6635590270, caea6bc68c925d63ca33d21b2255f47181943d61 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ aef69d54755d45edefbf347a51efd1673d7daed9, < f35e85a9d919d7954d9a7752e4644c0b403ad025
Fixed in
  • f35e85a9d919d7954d9a7752e4644c0b403ad025
LinuxLinuxAffected
  • ≥ aef69d54755d45edefbf347a51efd1673d7daed9, < cf9732fd6c4f2f803ccfc46d89489b6635590270
Fixed in
  • cf9732fd6c4f2f803ccfc46d89489b6635590270
LinuxLinuxAffected
  • ≥ aef69d54755d45edefbf347a51efd1673d7daed9, < caea6bc68c925d63ca33d21b2255f47181943d61
Fixed in
  • caea6bc68c925d63ca33d21b2255f47181943d61
LinuxLinuxAffected
  • ≥ aef69d54755d45edefbf347a51efd1673d7daed9, < c5e47cf9a6cffef73a1ed40b3648e6097aac165a
Fixed in
  • c5e47cf9a6cffef73a1ed40b3648e6097aac165a
LinuxLinuxAffected
  • ≥ aef69d54755d45edefbf347a51efd1673d7daed9, < 067887ff93fddbb3a3fb84c900bc654ecfe5ba61
Fixed in
  • 067887ff93fddbb3a3fb84c900bc654ecfe5ba61
LinuxLinuxAffected
  • ≥ aef69d54755d45edefbf347a51efd1673d7daed9, < 47ef04cd13d38010b580056a9d8840aaab944841
Fixed in
  • 47ef04cd13d38010b580056a9d8840aaab944841

AI-suggested

This vulnerability has been fixed in the Linux kernel. Users and administrators should update to a kernel version that includes the fix identified by the commits listed in the established facts. No additional mitigation steps are required once the fixed kernel version is deployed.

Description

A vulnerability in the Linux kernel's media subsystem (v4l2-fwnode) caused the sensor driver's module owner reference to be overwritten with NULL during asynchronous subdevice registration. This flaw could allow the sensor module to be removed prematurely while still in use, potentially leading to instability or crashes. The issue was fixed by changing the registration function to explicitly pass the correct module owner, ensuring proper reference counting.

References

Community reviews

Loading reviews…