CVE-2026-68205
CVE CVE-2026-68205EUVD EUVD-2026-55306Published 2026-08-10T12:00:24.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.1.6; patch: 6.12.101; 4.15; aef69d54755d45edefbf347a51efd1673d7daed9 <06cb687a5132fcffe624c0070576ab852ac6b568; patch: 6.6.151; aef69d54755d45edefbf347a51efd1673d7daed9 <cf9732fd6c4f2f803ccfc46d89489b6635590270; aef69d54755d45edefbf347a51efd1673d7daed9 <caea6bc68c925d63ca33d21b2255f47181943d61; aef69d54755d45edefbf347a51efd1673d7daed9 <47ef04cd13d38010b580056a9d8840aaab944841; patch: 6.18.42; patch: 0; patch: 7.2-rc1; aef69d54755d45edefbf347a51efd1673d7daed9 <067887ff93fddbb3a3fb84c900bc654ecfe5ba61
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.