CVE-2026-47104: 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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-47104 is a libusb memory-read bug fixed in 1.0.30. A malformed USB descriptor can make affected software read one byte past an allocated buffer and crash or fail, creating denial-of-service risk. The main concern is systems or applications that process USB devices, especially with USB passthrough in virtualized environments.
Executive priority
Treat this as a moderate availability issue, not an emergency breach indicator. Prioritize patching on virtualization hosts, endpoint tools, hardware-management software, and products that parse USB devices. Business urgency rises where crashes could interrupt operations or tenant isolation assumptions depend on USB passthrough controls.
Technical view
libusb before 1.0.30 has a CWE-125 out-of-bounds read in parse_iad_array() in descriptor.c. The described flaw involves a malformed descriptor length edge case where validation uses the original buffer size instead of remaining buffer size. The recorded CVSS 4.0 score is 5.1 with local attack vector and low availability impact.
Likely exposure
Exposure is most likely where libusb is installed directly, bundled into applications, or statically linked into software that enumerates USB descriptors. Virtualized environments allowing USB passthrough are specifically noted. Internet-facing exposure is not indicated by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The described attacker position is local or virtualized USB access without privileges or user interaction. Public issue, pull request, advisory, and patch references exist, so defenders should assume technical details are available.
Researcher notes
The available evidence supports a one-byte out-of-bounds read with denial-of-service impact. The patch, issue, and pull request should be reviewed for exact code-level behavior. Do not expand scope beyond libusb before 1.0.30 unless downstream vendors confirm affected bundled copies.
Mitigation direction
Upgrade libusb to version 1.0.30 or a vendor-provided fixed build.
Inventory applications and appliances that bundle or statically link libusb.
Restrict USB passthrough to trusted users and guests where feasible.
Track operating system and package vendor advisories for fixed downstream builds.
Restart or redeploy affected applications after updating the library.
Validation and detection
Confirm installed libusb versions are 1.0.30 or vendor-fixed builds.
Review SBOMs and dependency manifests for libusb before 1.0.30.
Check virtualization settings for unnecessary USB passthrough exposure.
Verify affected applications still handle normal USB descriptor parsing after updates.
Attach remediation evidence to vulnerability-management tickets.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.