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

> A use-after-free vulnerability in the Linux kernel's uvcvideo driver allows attackers to execute arbitrary code or escalate privileges via dangling pointers.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-57772, AZL-57950, BELL-CVE-2024-58002, DEBIAN-CVE-2024-58002, GHSA-qc22-v4cr-4rv7, ROOT-OS-UBUNTU-2404-CVE-2024-58002, UBUNTU-CVE-2024-58002

## What is CVE-2024-58002?

CVE-2024-58002 is a high-severity use after free vulnerability in Linux kernel, published on 27 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-58002?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-58002?

Apply the vendor's patch.

## Is CVE-2024-58002 being exploited?

There is no known exploitation of CVE-2024-58002 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58002 and fix it if it is affected.

What it is: CVE-2024-58002 is a high-severity use after free vulnerability in Linux kernel, published on 27 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58002 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-58002/ (Markdown: https://insights.sbomify.com/CVE-2024-58002/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58002
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58002
- OSV: https://osv.dev/vulnerability/CVE-2024-58002

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-58002/
Summaries are generated and may contain mistakes; the official description above is the record.