Kernel-memory disclosure via short USB interrupt packets
Published Jul 19, 2026 · Updated Jul 19, 2026
Out-of-bounds read in the mct_u232 USB serial driver in the Linux Kernel allows physically proximate attackers to expose kernel memory. The mct_u232_read_int_callback function interprets data[0] and data[1] without first ensuring that the interrupt transfer contains two bytes, so stale or uninitialized slab data reaches user space. A crafted short interrupt-in packet from a connected MCT U232-compatible USB device is required, and the reported consequence is limited to information disclosure.
Summary
What happened
Out-of-bounds read in the mct_u232 USB serial driver in the Linux Kernel allows physically proximate attackers to expose kernel memory. The mct_u232_read_int_callback function interprets data[0] and data[1] without first ensuring that the interrupt transfer contains two bytes, so stale or uninitialized slab data reaches user space. A crafted short interrupt-in packet from a connected MCT U232-compatible USB device is required, and the reported consequence is limited to information disclosure.
The record
- CVE
- CVE-2026-63897
- 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <245aba83e3c288e176ed037a1f6b618b09e92ed8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <631b8b7c456567f7a8d26f6fc354c8dd9cc9f832
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <70bb9a2661d34b93a9b83cf83e2b76289a712ef0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <82b48d70bced1ec8e5f676d1fd5eccc7a44dc418
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8b93ee5baeef6efabee2c3381907733ad2dbc883
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a093f3e0c03d25a86d747a655d4b9322ffb2ed87
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed260b56bc9fc878e5dcbb866eab8af0688e0e67
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f06bcaba29707f060706483b2020d3cafbe98f9f
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
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