CVE-2024-58002 is a use-after-free vulnerability in the Linux kernel uvcvideo media driver. During an asynchronous control operation, the driver retains a pointer to the file handle that initiated the request. If that file descriptor is closed before the device completes the operation, the file-handle structure is freed while pending asynchronous controls still reference it. Later completion handling can dereference these dangling pointers. The fix clears pending references associated with the file handle during driver release handling and tracks pending asynchronous operations to avoid overhead when none exist.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel UVC video-driver issue involving dangling pointers.
A Linux kernel uvcvideo media-driver vulnerability involving dangling pointers.
A Linux kernel UVC video driver flaw involving dangling pointers.
A dangling-pointer vulnerability in the Linux kernel uvcvideo media driver.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.