Strix
26.1K

CVE-2026-68207

Unknown

Last modified

CVE-2026-68207 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: media: ti: vpe: unwind v4l2 device registration on probe error If the vpe_top resource is missing, vpe_probe() returns -ENODEV after v4l2_device_register() has succeeded. Probe failures do not call the driver's remove callback, so the v4l2 device remains registered on that error path. Route that failure through the existing v4l2_device_unregister() unwind label, matching the other errors after v4l2_device_register()..

Description

In the Linux kernel, the following vulnerability has been resolved: media: ti: vpe: unwind v4l2 device registration on probe error If the vpe_top resource is missing, vpe_probe() returns -ENODEV after v4l2_device_register() has succeeded. Probe failures do not call the driver's remove callback, so the v4l2 device remains registered on that error path. Route that failure through the existing v4l2_device_unregister() unwind label, matching the other errors after v4l2_device_register().

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 4d59c7d455853edca990848b1cb7c482b4628f32, < 4ecf0cc0cf59032a89bcdf36fbbb03bff5455fd9; >= 4d59c7d455853edca990848b1cb7c482b4628f32, < 7d383357905de975e1dbde639e5fa7477075d104; >= 4d59c7d455853edca990848b1cb7c482b4628f32, < 7e6521dd747eca3cb3d4cd3ddcf20f266494f63d; >= 4d59c7d455853edca990848b1cb7c482b4628f32, < fcbbaf9cb9722a82f0221c56114037fc537f4ada; >= 4d59c7d455853edca990848b1cb7c482b4628f32, < e0f1c9a90ef665f2587c274a8fed59f2dfc575a6
LinuxLinux5.5

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68207?
In the Linux kernel, the following vulnerability has been resolved: media: ti: vpe: unwind v4l2 device registration on probe error If the vpe_top resource is missing, vpe_probe() returns -ENODEV after v4l2_device_register() has succeeded. Probe failures do not call the driver's remove callback, so the v4l2 device remains registered on that error path. Route that failure through the existing v4l2_device_unregister() unwind label, matching the other errors after v4l2_device_register().
How severe is CVE-2026-68207?
Severity scoring for CVE-2026-68207 is pending analysis.
How do I fix CVE-2026-68207?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-68207?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST