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-68205media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor()

Description

In the Linux kernel, the following vulnerability has been resolved: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() The v4l2 helper v4l2_async_register_subdev_sensor() calls v4l2_async_register_subdev(), which is a macro that expands to __v4l2_async_register_subdev(sd,THIS_MODULE). Since the macro is expanded inside v4l2-fwnode.c, THIS_MODULE resolves to the v4l2-fwnode module rather than the sensor driver module that originally set sd->owner. When v4l2-fwnode is built-in, THIS_MODULE evaluates to NULL, which then overwrites the sensor driver's owner with NULL. This causes the problem that the sensor module's reference count is never incremented during async registration, so the module can be removed while the subdevice is still in use by a notifier (e.g., a CSI-2 receiver bridge driver). Fix this by renaming v4l2_async_register_subdev_sensor() to __v4l2_async_register_subdev_sensor() with an added explicit module argument and introducing a wrapper macro: #define v4l2_async_register_subdev_sensor(sd) \ __v4l2_async_register_subdev_sensor(sd, THIS_MODULE) This ensures the sensor driver module is properly referenced even when the sensor driver does not init the owner field before calling v4l2_async_register_subdev_sensor() and prevents premature module removal.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected aef69d54755d45edefbf347a51efd1673d7daed9 – < f35e85a9d919d7954d9a7752e4644c0b403ad025
    • affected aef69d54755d45edefbf347a51efd1673d7daed9 – < c5e47cf9a6cffef73a1ed40b3648e6097aac165a
    • affected aef69d54755d45edefbf347a51efd1673d7daed9 – < 47ef04cd13d38010b580056a9d8840aaab944841
    • affected aef69d54755d45edefbf347a51efd1673d7daed9 – < caea6bc68c925d63ca33d21b2255f47181943d61
    • affected aef69d54755d45edefbf347a51efd1673d7daed9 – < cf9732fd6c4f2f803ccfc46d89489b6635590270
    • affected aef69d54755d45edefbf347a51efd1673d7daed9 – < 067887ff93fddbb3a3fb84c900bc654ecfe5ba61
    • affected aef69d54755d45edefbf347a51efd1673d7daed9 – < 06cb687a5132fcffe624c0070576ab852ac6b568
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 5.10.266 – ≤ 5.10.*
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .