LiveActive security incident?Get immediate response
CVE Record

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().

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
high
Sources
4

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-58059 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-58059Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc5fe3ed618f995b4a903e574bf2e993cdebeefca, c5fe3ed618f995b4a903e574bf2e993cdebeefcaunaffected
LinuxLinux6.13, 0, 6.13.2, 6.14affected
Weakness

CWE details

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.