Kernel memory corruption via unchecked USB command length
Published Aug 15, 2026 · Updated Aug 15, 2026
Out-of-bounds write in affected Linux kernel builds allows physically proximate attackers to corrupt kernel memory through crafted USB commands. The kvaser_usb_leaf_wait_cmd() path trusts the device-supplied length and copies a matching command into a fixed-size struct kvaser_cmd without confirming that the source contains a full header or that the command fits the USB buffer item and destination. Physical access and a Kvaser USB CAN device capable of returning a malformed command are required; the overwrite can corrupt kernel memory and interrupt the host.
Summary
What happened
Out-of-bounds write in affected Linux kernel builds allows physically proximate attackers to corrupt kernel memory through crafted USB commands. The kvaser_usb_leaf_wait_cmd() path trusts the device-supplied length and copies a matching command into a fixed-size struct kvaser_cmd without confirming that the source contains a full header or that the command fits the USB buffer item and destination. Physical access and a Kvaser USB CAN device capable of returning a malformed command are required; the overwrite can corrupt kernel memory and interrupt the host.
The record
- CVE
- CVE-2026-74458
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- 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=080f40a6fa28dab299da7a652e444b1e2d9231e7 <0293dd153f9dbc1ddf5dacdccc76b363bce4a8ee
- Affected versionversion=080f40a6fa28dab299da7a652e444b1e2d9231e7 <185cb1fa38142a3cbf223dd8b3abb24217f330d3
- Affected versionversion=080f40a6fa28dab299da7a652e444b1e2d9231e7 <21f0465fd86d77794aaed8e05f833634f68d178d
- Affected versionversion=080f40a6fa28dab299da7a652e444b1e2d9231e7 <3d0897ec623e422695d70d80ae456f89476c5328
- Affected versionversion=080f40a6fa28dab299da7a652e444b1e2d9231e7 <695aea154bb2d453e6daada1510972fafd075285
- Affected versionversion=3.8
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