Out-of-bounds read via short USBTMC notification
Published Jul 19, 2026 · Updated Jul 19, 2026
Out-of-bounds read in the Linux Kernel USBTMC driver allows physically proximate attackers to submit short interrupt-IN notifications. The usbtmc_interrupt() callback reads the first two bytes of iin_buffer without first verifying that urb->actual_length contains the two-byte header, so a short transfer causes an out-of-bounds read or consumes stale buffer data. Reachability requires a connected USBTMC device with an optional interrupt-IN endpoint; published material does not establish data disclosure or a kernel crash.
Summary
What happened
Out-of-bounds read in the Linux Kernel USBTMC driver allows physically proximate attackers to submit short interrupt-IN notifications. The usbtmc_interrupt() callback reads the first two bytes of iin_buffer without first verifying that urb->actual_length contains the two-byte header, so a short transfer causes an out-of-bounds read or consumes stale buffer data. Reachability requires a connected USBTMC device with an optional interrupt-IN endpoint; published material does not establish data disclosure or a kernel crash.
The record
- CVE
- CVE-2026-63904
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=4.6
- Affected versionversion=dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 <52f2ad3f7e5eb3b5908e1d685d4342519dc9cfcd
- Affected versionversion=dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 <5de7df75ef3a2756b25fe3d582a4a2970444fe5a
- Affected versionversion=dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 <69020fa089f1bf0e1a10a15265f31b143a846409
- Affected versionversion=dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 <75f6d3da2cc646983f41807ef98851569c12bca9
- Affected versionversion=dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 <ae87f505917e703ae3b487d9663d78826ff43608
- Affected versionversion=dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 <e3eec3005de44e7f37d8d7724be636446516ab42
- Affected versionversion=dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 <e794bd67b3faf98af46f958897f6b91412c7d2a9
- Affected versionversion=dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 <f141b01eaa58ac7e323931d670318aa247bff087
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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