Kernel memory corruption via premature device release
Published Sep 13, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux DWC3 ST USB driver from 3.18 allows local users to corrupt kernel memory by triggering a device-probe error. The undo_platform_dev_alloc branch drops the probed device's reference despite allocating no platform device, releasing resources before devm cleanup. Low-privileged local access and a probe failure on a system using the ST DWC3 driver are required; the stale references permit a kernel crash or memory corruption.
Summary
What happened
Use-after-free in the Linux DWC3 ST USB driver from 3.18 allows local users to corrupt kernel memory by triggering a device-probe error. The undo_platform_dev_alloc branch drops the probed device's reference despite allocating no platform device, releasing resources before devm cleanup. Low-privileged local access and a probe failure on a system using the ST DWC3 driver are required; the stale references permit a kernel crash or memory corruption.
The record
- CVE
- CVE-2024-46674
- Published
- Sep 13, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=3.18
- Affected versionversion=f83fca0707c66e36f14efef7f68702cb12de70b7 <060f41243ad7f6f5249fa7290dda0c01f723d12d
- Affected versionversion=f83fca0707c66e36f14efef7f68702cb12de70b7 <1de989668708ce5875efc9d669d227212aeb9a90
- Affected versionversion=f83fca0707c66e36f14efef7f68702cb12de70b7 <4c6735299540f3c82a5033d35be76a5c42e0fb18
- Affected versionversion=f83fca0707c66e36f14efef7f68702cb12de70b7 <6aee4c5635d81f4809c3b9f0c198a65adfbb2ada
- Affected versionversion=f83fca0707c66e36f14efef7f68702cb12de70b7 <b0979a885b9d4df2a25b88e9d444ccaa5f9f495c
- Affected versionversion=f83fca0707c66e36f14efef7f68702cb12de70b7 <ddfcfeba891064b88bb844208b43bef2ef970f0c
- Affected versionversion=f83fca0707c66e36f14efef7f68702cb12de70b7 <e1e5e8ea2731150d5ba7c707f9e02fafebcfeb49
- Affected versionversion=f83fca0707c66e36f14efef7f68702cb12de70b7 <f3498650df0805c75b4e1c94d07423c46cbf4ce1
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