CVE-2026-68207

Stale V4L2 registration via incomplete probe unwind

Published Aug 10, 2026 · Updated Aug 10, 2026

Resource cleanup error in the TI VPE driver in affected Linux kernel branches leaves a V4L2 device registered after probe failure. vpe_probe() returns after a missing vpe_top resource without calling v4l2_device_unregister(), although registration has already succeeded. The condition requires a TI VPE platform configuration lacking that resource; published material identifies only the stale registration and no user-triggerable path or further impact.

CVSS severityUnavailable
Unscored
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Resource cleanup error in the TI VPE driver in affected Linux kernel branches leaves a V4L2 device registered after probe failure. vpe_probe() returns after a missing vpe_top resource without calling v4l2_device_unregister(), although registration has already succeeded. The condition requires a TI VPE platform configuration lacking that resource; published material identifies only the stale registration and no user-triggerable path or further impact.

The record

CVE
CVE-2026-68207
Published
Aug 10, 2026
Updated
Aug 10, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4d59c7d455853edca990848b1cb7c482b4628f32 <4ecf0cc0cf59032a89bcdf36fbbb03bff5455fd9
  2. Affected versionversion=4d59c7d455853edca990848b1cb7c482b4628f32 <7d383357905de975e1dbde639e5fa7477075d104
  3. Affected versionversion=4d59c7d455853edca990848b1cb7c482b4628f32 <7e6521dd747eca3cb3d4cd3ddcf20f266494f63d
  4. Affected versionversion=4d59c7d455853edca990848b1cb7c482b4628f32 <e0f1c9a90ef665f2587c274a8fed59f2dfc575a6
  5. Affected versionversion=4d59c7d455853edca990848b1cb7c482b4628f32 <fcbbaf9cb9722a82f0221c56114037fc537f4ada
  6. Affected versionversion=5.5

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=4d59c7d455853edca990848b1cb7c482b4628f32 <4ecf0cc0cf59032a89bcdf36fbbb03bff5455fd9; version=4d59c7d455853edca990848b1cb7c482b4628f32 <7d383357905de975e1dbde639e5fa7477075d104; version=4d59c7d455853edca990848b1cb7c482b4628f32 <7e6521dd747eca3cb3d4cd3ddcf20f266494f63d; version=4d59c7d455853edca990848b1cb7c482b4628f32 <e0f1c9a90ef665f2587c274a8fed59f2dfc575a6; version=4d59c7d455853edca990848b1cb7c482b4628f32 <fcbbaf9cb9722a82f0221c56114037fc537f4ada; version=5.5

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo