Kernel memory corruption via dangling status pointer
Published Feb 27, 2025 · Updated May 11, 2026
A double free in Linux uvcvideo allows local users to corrupt kernel memory when status interrupt-URB allocation fails. uvc_status_init frees dev->status after int_urb allocation fails but leaves the dangling pointer for uvc_status_cleanup to free again. Reachability requires the uvcvideo status-initialization error path, and the second free exposes the host to a kernel crash or altered kernel execution.
Summary
What happened
A double free in Linux uvcvideo allows local users to corrupt kernel memory when status interrupt-URB allocation fails. uvc_status_init frees dev->status after int_urb allocation fails but leaves the dangling pointer for uvc_status_cleanup to free again. Reachability requires the uvcvideo status-initialization error path, and the second free exposes the host to a kernel crash or altered kernel execution.
The record
- CVE
- CVE-2024-57980
- Published
- Feb 27, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.28
- Affected versionversion=a31a4055473bf0a7b2b06cb2262347200d0711e1 <3ba8884a56a3eb97c22f0ce0e4dd410d4ca4c277
- Affected versionversion=a31a4055473bf0a7b2b06cb2262347200d0711e1 <6c36dcd662ec5276782838660f8533a7cb26be49
- Affected versionversion=a31a4055473bf0a7b2b06cb2262347200d0711e1 <87522ef165e5b6de8ef98cc318f3335166a1512c
- Affected versionversion=a31a4055473bf0a7b2b06cb2262347200d0711e1 <9232719ac9ce4d5c213cebda23d72aec3e1c4c0d
- Affected versionversion=a31a4055473bf0a7b2b06cb2262347200d0711e1 <c6ef3a7fa97ec823a1e1af9085cf13db9f7b3bac
- Affected versionversion=a31a4055473bf0a7b2b06cb2262347200d0711e1 <d1f8e69eec91d5a75ef079778a5d0151db2a7f22
- Affected versionversion=a31a4055473bf0a7b2b06cb2262347200d0711e1 <d6e5ba2516c5bef87c1fcb8189b6f3cad7c64b2d
- Affected versionversion=a31a4055473bf0a7b2b06cb2262347200d0711e1 <d8e63dd7b6683969d3d47c7b8e9635f96d554ad4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo