CVE-2026-68205: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor()

Published Aug 10, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

media: v4l2-fwnode: Fix subdev owner overwritten in v4l2asyncregistersubdevsensor()

The v4l2 helper v4l2asyncregistersubdevsensor() calls v4l2asyncregistersubdev(), which is a macro that expands to v4l2asyncregistersubdev(sd,THISMODULE). Since the macro is expanded inside v4l2-fwnode.c, THISMODULE resolves to the v4l2-fwnode module rather than the sensor driver module that originally set sd->owner. When v4l2-fwnode is built-in, THISMODULE 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 v4l2asyncregistersubdevsensor() to v4l2asyncregistersubdevsensor() with an added explicit module argument and introducing a wrapper macro: #define v4l2asyncregistersubdevsensor(sd) \ v4l2asyncregistersubdevsensor(sd, THISMODULE)

This ensures the sensor driver module is properly referenced even when the sensor driver does not init the owner field before calling v4l2asyncregistersubdevsensor() and prevents premature module removal.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Linux kernel (media: v4l2-fwnode) to a version that resolves this vulnerability.

    Patch media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor()

Event History

Aug 10, 2026
CVE Published
via MITRE·12:00 PM
Data Sourced
via MITRE·12:00 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68205?

The severity of CVE-2026-68205 is rated at 34.

2

How do I fix CVE-2026-68205?

To fix CVE-2026-68205, update the Linux kernel to the latest version that includes the patch for this vulnerability.

3

What components are affected by CVE-2026-68205?

CVE-2026-68205 affects the v4l2 subsystem in the Linux kernel.

4

What is the impact of CVE-2026-68205?

The impact of CVE-2026-68205 involves the potential overwriting of subdev owner information in the v4l2_async_register_subdev_sensor() function.

5

When was CVE-2026-68205 published?

CVE-2026-68205 was published on August 10, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203