CVE-2026-68205media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 23, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from aef69d54755d45edefbf347a51efd1673d7daed9 before f35e85a9d919d7954d9a7752e4644c0b403ad025; from aef69d54755d45edefbf347a51efd1673d7daed9 before c5e47cf9a6cffef73a1ed40b3648e6097aac165a; from aef69d54755d45edefbf347a51efd1673d7daed9 before 47ef04cd13d38010b580056a9d8840aaab944841; from aef69d54755d45edefbf347a51efd1673d7daed9 before caea6bc68c925d63ca33d21b2255f47181943d61; from aef69d54755d45edefbf347a51efd1673d7daed9 before cf9732fd6c4f2f803ccfc46d89489b6635590270; from aef69d54755d45edefbf347a51efd1673d7daed9 before 067887ff93fddbb3a3fb84c900bc654ecfe5ba61; from aef69d54755d45edefbf347a51efd1673d7daed9 before 06cb687a5132fcffe624c0070576ab852ac6b568 | CNA record |
References
- https://git.kernel.org/stable/c/f35e85a9d919d7954d9a7752e4644c0b403ad025
- https://git.kernel.org/stable/c/c5e47cf9a6cffef73a1ed40b3648e6097aac165a
- https://git.kernel.org/stable/c/47ef04cd13d38010b580056a9d8840aaab944841
- https://git.kernel.org/stable/c/caea6bc68c925d63ca33d21b2255f47181943d61
- https://git.kernel.org/stable/c/cf9732fd6c4f2f803ccfc46d89489b6635590270
- https://git.kernel.org/stable/c/067887ff93fddbb3a3fb84c900bc654ecfe5ba61
- https://git.kernel.org/stable/c/06cb687a5132fcffe624c0070576ab852ac6b568
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.