Kernel memory disclosure via wrong URB buffer logging
Published Aug 15, 2026 · Updated Aug 15, 2026
Out-of-bounds read in the Linux kernel ims-pcu driver allows physically proximate attackers to disclose adjacent kernel memory through debug logging. The ims_pcu_irq() debug path always prints pcu->urb_in_buf even when the interrupt belongs to the control URB, whose data is held in pcu->urb_ctrl_buf; a control transfer longer than pcu->max_in_size therefore reads past the input buffer. Exploitation requires access to a compatible USB device path, and the exposed bytes enter kernel debug output rather than a network response.
Summary
What happened
Out-of-bounds read in the Linux kernel ims-pcu driver allows physically proximate attackers to disclose adjacent kernel memory through debug logging. The ims_pcu_irq() debug path always prints pcu->urb_in_buf even when the interrupt belongs to the control URB, whose data is held in pcu->urb_ctrl_buf; a control transfer longer than pcu->max_in_size therefore reads past the input buffer. Exploitation requires access to a compatible USB device path, and the exposed bytes enter kernel debug output rather than a network response.
The record
- CVE
- CVE-2026-72076
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- 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 <20fbf3ca0259d00664d1ede88837e1f11b49a88e
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <3fd7c0ace245334f2a0bd29fdcb680ad56e9b275
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <403b0a6970b1084bb27907c0f8225801fdd0fe1d
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <4d2553e9a76a11500ec670cbe16b7fd3da4832de
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <9c964fc9507aeab74376ba9f892cf84ad6950dfe
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <b746e853721dee91e4234c033d1b90f4605705bb
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <e6153407d7edabc6ff98f0fda415d556c0bcb57a
- Affected versionversion=628329d52474323938a03826941e166bc7c8eff4 <f97bfc1a0766802a99167b3dc62d1ee7dca929fe
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