Kernel crash via premature V4L2 device registration
Published May 17, 2024 · Updated Aug 5, 2026
Race condition in the Linux tc358743 media driver allows local users to crash affected kernels through V4L2 subdevice access. The tc358743_probe function registers its asynchronous subdevice before initializing the mutex, work queues, hardware, and related resources, exposing partially initialized state to userspace. Exploitation requires a tc358743 device and access to its V4L2 node during driver probing; the published impact is limited to service interruption.
Summary
What happened
Race condition in the Linux tc358743 media driver allows local users to crash affected kernels through V4L2 subdevice access. The tc358743_probe function registers its asynchronous subdevice before initializing the mutex, work queues, hardware, and related resources, exposing partially initialized state to userspace. Exploitation requires a tc358743 device and access to its V4L2 node during driver probing; the published impact is limited to service interruption.
The record
- CVE
- CVE-2024-35830
- Published
- May 17, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
- Affected versionversion=4.3
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <17c2650de14842c25c569cbb2126c421489a3a24
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <4f1490a5d7a0472ee5d9f36547bc4ba46be755c7
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <610f20e5cf35ca9c0992693cae0dd8643ce932e7
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <87399f1ff92203d65f1febf5919429f4bb613a02
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <8ba8db9786b55047df5ad3db3e01dd886687a77d
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <b8505a1aee8f1edc9d16d72ae09c93de086e2a1a
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <c915c46a25c3efb084c4f5e69a053d7f7a635496
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <daf21394f9898fb9f0698c3e50de08132d2164e6
- Affected versionversion=4c5211a100399c3823563193dd881dcb3b7d24fc <edbb3226c985469a2f8eb69885055c9f5550f468
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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