Kernel memory corruption via spoofed USB interface
Published Aug 15, 2026 · Updated Aug 15, 2026
Use-after-free in the Linux kernel ims-pcu driver allows physically proximate attackers to trigger unsafe memory reuse with a malicious USB device. ims_pcu_disconnect() identifies the control interface by class alone, so a same-class data interface causes cleanup before the actual control interface is unbound. Exploitation requires a crafted USB interface and can cause use-after-free or double-free; code execution has not been established.
Summary
What happened
Use-after-free in the Linux kernel ims-pcu driver allows physically proximate attackers to trigger unsafe memory reuse with a malicious USB device. ims_pcu_disconnect() identifies the control interface by class alone, so a same-class data interface causes cleanup before the actual control interface is unbound. Exploitation requires a crafted USB interface and can cause use-after-free or double-free; code execution has not been established.
The record
- CVE
- CVE-2026-72079
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, CWE-826, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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.10
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <293388e42e5c0865204de6f36bfb8662156fce3b
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <315f269ea04bc1477ab9bf351e939623d12a1621
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <462a999917755a3bf77448dfd64307963cf0a9f0
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <6a6c373e6a82eddc522342c8a8db7072c65f2b56
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <6aacc18004b1a915ccb8a829d30279a37988066e
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <921abbb33887052e46b1b77299f87a3c741dc580
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <a4b3f4d42fbf58f06f0d49e37a9d0d9392eca338
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <bf0b58ba489d0bdaa18c7dd8beeaeb954dd7dbb7
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.
Weakness, pattern, technique
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