Hub-state corruption via unchecked bit shift
Published Aug 15, 2026 · Updated Aug 15, 2026
Incorrect bit shifting in the Linux kernel MAX3421 USB host driver allows local users to corrupt virtual root-hub port status. In max3421_hub_control(), the ClearPortFeature and SetPortFeature default paths shift 1 by unchecked wValue before OR-ing it into port_status. The caller needs local access to the root hub through /dev/bus/usb and a wValue of at least 32; the undefined shift can alter normally immutable change bits, bypass state checks, and confuse hub status.
Summary
What happened
Incorrect bit shifting in the Linux kernel MAX3421 USB host driver allows local users to corrupt virtual root-hub port status. In max3421_hub_control(), the ClearPortFeature and SetPortFeature default paths shift 1 by unchecked wValue before OR-ing it into port_status. The caller needs local access to the root hub through /dev/bus/usb and a wValue of at least 32; the undefined shift can alter normally immutable change bits, bypass state checks, and confuse hub status.
The record
- CVE
- CVE-2026-72483
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-1335, CWE-682
- Attack vector
- local
- Privileges
- authenticated
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=2d53139f31626bad6f8983d8e519ddde2cbba921 <00dd025324b56d39d37e57a08f473dab3a660f30
- Affected versionversion=2d53139f31626bad6f8983d8e519ddde2cbba921 <02d03c61e8a7b016956acb48e8a2512d16d87517
- Affected versionversion=2d53139f31626bad6f8983d8e519ddde2cbba921 <08b1d4cab0230697bc74c63fc4e40170a7559c54
- Affected versionversion=2d53139f31626bad6f8983d8e519ddde2cbba921 <3be5f24e8270ba53b3c814d13689bb8644c86237
- Affected versionversion=2d53139f31626bad6f8983d8e519ddde2cbba921 <4da073d57176d8e1c2bca34febfbc81d2560c1a5
- Affected versionversion=2d53139f31626bad6f8983d8e519ddde2cbba921 <cff06b03b530ae1fe8a13e93a7848f2130e00fb4
- Affected versionversion=2d53139f31626bad6f8983d8e519ddde2cbba921 <d512bdefd241b98f4d7bcb5bab5614a86411fad4
- Affected versionversion=2d53139f31626bad6f8983d8e519ddde2cbba921 <e5fa9d8f40746ec3447335c9642c03410f5fd3af
- Affected versionversion=3.16
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.
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