CVE-2026-68205

Unknown

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.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedAug 10, 2026
First seenAug 10, 2026

How to fix

Update
  • Linux Linuxf35e85a9d919d7954d9a7752e4644c0b403ad025, c5e47cf9a6cffef73a1ed40b3648e6097aac165a, 47ef04cd13d38010b580056a9d8840aaab944841, caea6bc68c925d63ca33d21b2255f47181943d61, cf9732fd6c4f2f803ccfc46d89489b6635590270, 067887ff93fddbb3a3fb84c900bc654ecfe5ba61, 06cb687a5132fcffe624c0070576ab852ac6b568 or later

Affected products

ProductAffected versionsFixed in
Linux Linuxaef69d54755d45edefbf347a51efd1673d7daed9 ≤ v < f35e85a9d919d7954d9a7752e4644c0b403ad025, aef69d54755d45edefbf347a51efd1673d7daed9 ≤ v < c5e47cf9a6cffef73a1ed40b3648e6097aac165a, aef69d54755d45edefbf347a51efd1673d7daed9 ≤ v < 47ef04cd13d38010b580056a9d8840aaab944841, aef69d54755d45edefbf347a51efd1673d7daed9 ≤ v < caea6bc68c925d63ca33d21b2255f47181943d61, aef69d54755d45edefbf347a51efd1673d7daed9 ≤ v < cf9732fd6c4f2f803ccfc46d89489b6635590270, aef69d54755d45edefbf347a51efd1673d7daed9 ≤ v < 067887ff93fddbb3a3fb84c900bc654ecfe5ba61, aef69d54755d45edefbf347a51efd1673d7daed9 ≤ v < 06cb687a5132fcffe624c0070576ab852ac6b568, 4.15f35e85a9d919d7954d9a7752e4644c0b403ad025, c5e47cf9a6cffef73a1ed40b3648e6097aac165a, 47ef04cd13d38010b580056a9d8840aaab944841, caea6bc68c925d63ca33d21b2255f47181943d61, cf9732fd6c4f2f803ccfc46d89489b6635590270, 067887ff93fddbb3a3fb84c900bc654ecfe5ba61, 06cb687a5132fcffe624c0070576ab852ac6b568

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.