media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor()
Summary
| CVE | CVE-2026-68205 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-10 13:20:08 UTC |
| Updated | 2026-08-10 13:20:08 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected aef69d54755d45edefbf347a51efd1673d7daed9 47ef04cd13d38010b580056a9d8840aaab944841 git |
Not specified |
| CNA |
Linux |
Linux |
affected aef69d54755d45edefbf347a51efd1673d7daed9 caea6bc68c925d63ca33d21b2255f47181943d61 git |
Not specified |
| CNA |
Linux |
Linux |
affected aef69d54755d45edefbf347a51efd1673d7daed9 cf9732fd6c4f2f803ccfc46d89489b6635590270 git |
Not specified |
| CNA |
Linux |
Linux |
affected aef69d54755d45edefbf347a51efd1673d7daed9 067887ff93fddbb3a3fb84c900bc654ecfe5ba61 git |
Not specified |
| CNA |
Linux |
Linux |
affected aef69d54755d45edefbf347a51efd1673d7daed9 06cb687a5132fcffe624c0070576ab852ac6b568 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.15 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.15 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.151 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.101 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.42 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.6 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/06cb687a5132fcffe624c0070576ab852ac6b568 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/47ef04cd13d38010b580056a9d8840aaab944841 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/067887ff93fddbb3a3fb84c900bc654ecfe5ba61 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/cf9732fd6c4f2f803ccfc46d89489b6635590270 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/caea6bc68c925d63ca33d21b2255f47181943d61 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.