LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58002: media: uvcvideo: Remove dangling pointers

In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Remove dangling pointers When an async control is written, we copy a pointer to the file handle that started the operation. That pointer will be used when the device is done. Which could be anytime in the future. If the user closes that file descriptor, its structure will be freed, and there will be one dangling pointer per pending async control, that the driver will try to use. Clean all the dangling pointers during release(). To avoid adding a performance penalty in the most common case (no async operation), a counter has been introduced with some logic to make sure that it is properly handled.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's Takemoderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2024-58002 is a Linux kernel uvcvideo driver flaw where a webcam-related async operation can keep using a file handle after it is closed. That creates a dangling pointer in kernel code. Business urgency depends on whether affected Linux kernels expose UVC camera devices to users or workloads.

Executive priority

Prioritize normal kernel patching, with faster action for shared Linux desktops, kiosk systems, developer workstations, and workloads exposing camera devices to untrusted users. There is no source-backed evidence of active exploitation in the provided bundle.

Technical view

The uvcvideo driver copied a file-handle pointer for async controls and later used it after the descriptor could be closed and freed. The kernel fix clears pending dangling pointers during release() and adds counting logic to avoid common-case performance cost.

Likely exposure

Linux systems using affected kernel builds with the uvcvideo driver and UVC camera or video devices are the main concern. Exposure is most relevant where local users, containers, services, or desktop sessions can access video device nodes.

Exploitation context

The provided sources do not show CISA KEV listing, active exploitation, public exploit code, CVSS, or CWE classification. The described condition is a kernel dangling-pointer issue, but the sources do not state a proven impact such as privilege escalation or denial of service.

Researcher notes

Focus validation on the async control release path in uvcvideo and distribution backport status. The bundle provides fix commits and Debian LTS advisories, but lacks CVSS, CWE, exploitability analysis, and concrete vulnerable version range semantics.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable uvcvideo fixes.
  • Check Debian LTS advisories if running Debian-based long-term support kernels.
  • Restrict access to video device nodes to users and services that need them.
  • Review vendor guidance before applying non-distribution kernel patches.

Validation and detection

  • Inventory Linux kernel versions and package advisory status across endpoints and servers.
  • Identify systems with uvcvideo loaded or UVC camera devices attached.
  • Confirm installed kernels include the relevant stable commits or distribution backports.
  • Review device permissions for /dev/video* on shared or multi-user systems.
Prepared
Confidence
medium
Sources
12

Public sources used

Based on public source material and reviewed before publication.

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-58002 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe5225c820c057537dc780244760e2e24c7d27366, e5225c820c057537dc780244760e2e24c7d27366, e5225c820c057537dc780244760e2e24c7d27366, e5225c820c057537dc780244760e2e24c7d27366, e5225c820c057537dc780244760e2e24c7d27366, e5225c820c057537dc780244760e2e24c7d27366, e5225c820c057537dc780244760e2e24c7d27366, e5225c820c057537dc780244760e2e24c7d27366unaffected
LinuxLinux4.19, 0, 5.4.291, 5.10.235, 5.15.179, 6.1.130, 6.6.80, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.