CVE-2024-35830: media: tc358743: register v4l2 async device only after successful setup
In the Linux kernel, the following vulnerability has been resolved:
media: tc358743: register v4l2 async device only after successful setup
Ensure the device has been setup correctly before registering the v4l2
async device, thus allowing userspace to access.
Security readout for executives and security teams
Plain-English summary
A Linux video-bridge driver could expose its userspace interface before hardware setup completed successfully. A low-privileged local user could then interact with an incompletely initialized device. The supplied CVSS 3.1 score is 7.8, but practical exposure depends on systems using the Toshiba TC358743 media driver.
Executive priority
Treat this as a targeted high-priority kernel issue, not an internet-wide emergency. Accelerate remediation for relevant video-capture and embedded systems, particularly multi-user systems or those running untrusted workloads. Other systems can follow normal kernel maintenance after confirming that the affected driver and hardware path are absent.
Technical view
The fix changes tc358743 initialization ordering so V4L2 asynchronous registration occurs only after successful device setup. Earlier registration could make the interface reachable from userspace after incomplete or failed initialization. The sources do not identify a precise corruption primitive, CWE, or tested exploit, so impacts beyond the supplied CVSS vector should not be assumed.
Likely exposure
Potential exposure is concentrated in Linux video-capture or embedded systems that initialize the tc358743 driver and associated hardware. Generic servers are less likely affected in practice. The bundle identifies numerous affected kernel releases, but its version data is not expressed as clear ranges; validate distribution backports instead of relying on version-string matching.
Exploitation context
The supplied CVSS vector describes local access with low privileges, low complexity, and no user interaction. No cited source reports active exploitation, and the bundle marks the CVE as absent from KEV. The public evidence also contains no proof-of-concept or exploitation details.
Researcher notes
The bundle provides nine stable-kernel fix commits and Debian LTS advisories, but no CWE, proof-of-concept, exploitation report, or detailed failure primitive. Validate vulnerable code and backports against distribution package sources because the supplied version list is ambiguous. Avoid inferring memory corruption or a specific privilege-escalation mechanism without additional evidence.
Mitigation direction
Update to a vendor-supported kernel containing the cited tc358743 registration-order fix.
Use distribution advisories to identify fixed packaged kernels and applicable backports.
Prioritize systems that initialize TC358743 hardware or permit untrusted local users.
If updating is delayed, consult vendor guidance; the bundle specifies no supported compensating control.
Validation and detection
Inventory exact running kernel and distribution package versions.
Determine whether the tc358743 driver is configured, loaded, and associated hardware is present.
Compare installed packages with vendor advisories and the cited stable-kernel fixes.
After updating, confirm the fixed kernel is running and the device initializes normally.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-35830 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.