libusb < 1.0.30 Out-of-Bounds Read in parse_iad_array()
libusb before version 1.0.30 contains a one-byte out-of-bounds read vulnerability in parse_iad_array() in descriptor.c that allows attackers to trigger a denial of service by supplying a malformed USB descriptor whose bLength equals size minus one, causing the bounds check to use the original buffer size instead of the remaining size. Attackers in virtualized environments with USB passthrough can supply crafted descriptors through libusb_get_active_interface_association_descriptors or libusb_get_interface_association_descriptors to read one byte past the end of the malloc allocation, resulting in a denial of service.
- Published
- May 27, 2026
- Updated
- Jul 14, 2026
- EPSS
- 0.2% · 8th percentile
- CWE
- CWE-125
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
20
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 5.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| libusb | libusb | cpe:2.3:a:libusb:libusb |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libusb libusbbefore 1.0.30
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
libusb libusb
- before 1.0.30affected · 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 | libusb-1.0 | all versions | — |
| Debian:14 | libusb-1.0 | before 2:1.0.30-1 | 2:1.0.30-1 |
| openSUSE:Leap 16.0 | libusb-1_0 | before 1.0.28-160000.3.1 | 1.0.28-160000.3.1 |
| PyPI | libusb | before 1.0.30 | 1.0.30 |
| Red Hat:hummingbird:1 | libusb1 | before 0:1.0.30-1.hum1 | 0:1.0.30-1.hum1 |
| Red Hat:hummingbird:1 | libusb1-devel-doc | before 0:1.0.30-1.hum1 | 0:1.0.30-1.hum1 |
| SUSE:Linux Micro 6.0 | libusb-1_0 | before 1.0.27-2.1 | 1.0.27-2.1 |
| SUSE:Linux Micro 6.1 | libusb-1_0 | before 1.0.27-slfo.1.1_2.1 | 1.0.27-slfo.1.1_2.1 |
| SUSE:Linux Micro 6.2 | libusb-1_0 | before 1.0.28-160000.3.1 | 1.0.28-160000.3.1 |
Same product
libusb: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-23679libusb < 1.0.30 NULL Pointer Dereference in parse_interface()27Monitor
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 |
|---|---|---|
| libusb libusb | 1.0.30 | Vendor (CNA) |
| debian:libusb-1.0 | 2:1.0.30-1 · Debian:14 | Package registry (OSV) |
| opensuse:libusb-1_0 | 1.0.28-160000.3.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| PyPI:libusb | 1.0.30 | Package registry (OSV) |
| red hat:libusb1 | 0:1.0.30-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libusb1-devel-doc | 0:1.0.30-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:libusb-1_0 | 1.0.27-2.1 · SUSE:Linux Micro 6.0 | 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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- @MarkLee131finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-236790 days apartlibusb < 1.0.30 NULL Pointer Dereference in parse_interface()27Monitor
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.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/libusb/libusb/commit/578ab76b4c434f8b204137ab6d7310689c7a9704
- github.com/libusb/libusb/issues/1813
- github.com/libusb/libusb/pull/1814
- github.com/libusb/libusb/releases/tag/v1.0.30
- www.vulncheck.com/advisories/libusb-out-of-bounds-read-in-parse-iad-array
Vendor advisories and official records. Exploit/PoC links are deliberately left out.