CVE-2026-72483: usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 00dd025324b56d39d37e57a08f473dab3a660f30, 02d03c61e8a7b016956acb48e8a2512d16d87517, 08b1d4cab0230697bc74c63fc4e40170a7559c54.
Low priority for now. Upgrade to Linux Linux 00dd025324b56d39d37e57a08f473dab3a660f30, 02d03c61e8a7b016956acb48e8a2512d16d87517, 08b1d4cab0230697bc74c63fc4e40170a7559c54 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control() The `max3421_hub_control()` function handles USB hub class requests to the virtual root hub. In the `default` branches of both the `ClearPortFeature` and `SetPortFeature` switch statements, it modifies `max3421_hcd->port_status` by left shifting 1 by the request's `value` parameter. However, it does not validate whether this shift will exceed the width of `port_status`. So if a malicious userspace task with access to the root hub via /dev/bus/usb/.../001 issues a USBDEVFS_CONTROL ioctl with `wValue` greater than or equal to 32, the left shift operation invokes shift-out-of-bounds undefined behavior. This results in arbitrary bit corruption of `port_status`, including the normally-immutable change bits, which can bypass internal state checks and confuse the hub status. Fix this by rejecting requests whose `value` exceeds the shift width before performing the shift. This issue was found using a KLEE-based symbolic execution tool for kernel drivers that I'm currently developing.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.16affected
- 2d53139f31626bad6f8983d8e519ddde2cbba921 and later · before e5fa9d8f40746ec3447335c9642c03410f5fd3afaffected · git
- 2d53139f31626bad6f8983d8e519ddde2cbba921 and later · before 08b1d4cab0230697bc74c63fc4e40170a7559c54affected · git
- 2d53139f31626bad6f8983d8e519ddde2cbba921 and later · before 3be5f24e8270ba53b3c814d13689bb8644c86237affected · git
- 2d53139f31626bad6f8983d8e519ddde2cbba921 and later · before d512bdefd241b98f4d7bcb5bab5614a86411fad4affected · git
- 2d53139f31626bad6f8983d8e519ddde2cbba921 and later · before 00dd025324b56d39d37e57a08f473dab3a660f30affected · git
- 2d53139f31626bad6f8983d8e519ddde2cbba921 and later · before 02d03c61e8a7b016956acb48e8a2512d16d87517affected · git
- 2d53139f31626bad6f8983d8e519ddde2cbba921 and later · before 4da073d57176d8e1c2bca34febfbc81d2560c1a5affected · git
- 2d53139f31626bad6f8983d8e519ddde2cbba921 and later · before cff06b03b530ae1fe8a13e93a7848f2130e00fb4affected · git
- before 3.16not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72481Aug 15, 2026 · iio: magnetometer: ak8975: fix potential kernel stack memory leak0Monitor
- ← EarlierCVE-2026-72482Aug 15, 2026 · gpib: fix double decrement of descriptor_busy in command_ioctl()31Monitor
- Later →CVE-2026-72484Aug 15, 2026 · staging: most: video: avoid double free on video register failure0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 00dd025324b56d39d37e57a08f473dab3a660f30 | Vendor (CNA) |
| Linux Linux | 02d03c61e8a7b016956acb48e8a2512d16d87517 | Vendor (CNA) |
| Linux Linux | 08b1d4cab0230697bc74c63fc4e40170a7559c54 | Vendor (CNA) |
| Linux Linux | 3be5f24e8270ba53b3c814d13689bb8644c86237 | Vendor (CNA) |
| Linux Linux | 4da073d57176d8e1c2bca34febfbc81d2560c1a5 | Vendor (CNA) |
| Linux Linux | cff06b03b530ae1fe8a13e93a7848f2130e00fb4 | Vendor (CNA) |
| Linux Linux | d512bdefd241b98f4d7bcb5bab5614a86411fad4 | Vendor (CNA) |
| Linux Linux | e5fa9d8f40746ec3447335c9642c03410f5fd3af | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/02d03c61e8a7b016956acb48e8a2512d16d87517
- git.kernel.org/stable/c/08b1d4cab0230697bc74c63fc4e40170a7559c54
- git.kernel.org/stable/c/3be5f24e8270ba53b3c814d13689bb8644c86237
- git.kernel.org/stable/c/4da073d57176d8e1c2bca34febfbc81d2560c1a5
- git.kernel.org/stable/c/cff06b03b530ae1fe8a13e93a7848f2130e00fb4
- git.kernel.org/stable/c/d512bdefd241b98f4d7bcb5bab5614a86411fad4
- git.kernel.org/stable/c/e5fa9d8f40746ec3447335c9642c03410f5fd3af
Vendor advisories and official records. Exploit/PoC links are deliberately left out.