CVE-2024-58059: media: uvcvideo: Fix deadlock during uvc_probe
In the Linux kernel, the following vulnerability has been resolved:
media: uvcvideo: Fix deadlock during uvc_probe
If uvc_probe() fails, it can end up calling uvc_status_unregister() before
uvc_status_init() is called.
Fix this by checking if dev->status is NULL or not in
uvc_status_unregister().
Security readout for executives and security teams
Plain-English summary
CVE-2024-58059 is a Linux kernel availability issue in the UVC video driver. If device probing fails in a specific order, the kernel can hit a deadlock. The business risk is local denial of service, not data theft or remote compromise based on the supplied sources.
Executive priority
Treat as routine-to-prioritized patching for Linux endpoints or appliances using camera support. It is not evidenced as remotely exploitable or actively exploited, but availability impact can matter on kiosks, workstations, embedded devices, or operational systems using video input.
Technical view
The flaw is in media uvcvideo during uvc_probe failure handling. uvc_status_unregister() could be called before uvc_status_init(), leading to deadlock. The kernel fix checks whether dev->status is NULL before unregistering. CVSS is 5.5: local, low complexity, low privilege, availability-only impact.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the uvcvideo driver present, especially systems using USB/UVC camera functionality. The supplied data lists Linux 6.13-related affected version information and stable kernel fixes, but not distribution package names.
Exploitation context
The supplied sources do not report active exploitation, and KEV is false. The CVSS vector indicates local access with low privileges and no user interaction. No network attack path is supported by the provided evidence.
Researcher notes
Evidence is limited to the CVE record and kernel stable references. The root cause is improper lock/resource handling around failed uvc_probe initialization. Avoid assuming exploitability beyond the local availability impact expressed in CVSS and the deadlock description.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
Prioritize systems using UVC or USB camera functionality.
Check distribution advisories for exact backported fixed package versions.
Restrict unnecessary local account and device access where practical until patched.
Validation and detection
Inventory Linux kernel versions on exposed fleets.
Confirm whether the uvcvideo driver is present or loaded.
Map installed kernels to vendor fixed package advisories.
Verify patched kernels include the referenced stable fix commits.
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.
cwe · low confidence lookup
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-667 · source CWE mapping
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.