libusb up to 1.0.29 parse_interface out-of-bounds

Summaryinfo

A vulnerability classified as problematic has been found in libusb up to 1.0.29. Affected by this issue is the function parse_interface. This manipulation causes out-of-bounds. The identification of this vulnerability is CVE-2026-23679. The attack can only be executed locally. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in libusb up to 1.0.29 and classified as problematic. Affected by this vulnerability is the function parse_interface. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect availability. The summary by CVE is:

libusb before version 1.0.30 contains a NULL pointer dereference vulnerability that allows attackers to crash applications by supplying a malformed USB configuration descriptor where an interface claims bNumEndpoints greater than zero but is followed by a class-specific descriptor whose bLength exceeds the remaining buffer size, causing parse_interface() to return early without allocating the endpoint array. Attackers can exploit this flaw through libusb_get_active_config_descriptor or libusb_get_config_descriptor by providing crafted descriptors via virtualized USB passthrough, file-based descriptor parsing, or network sources, causing any application iterating over endpoints to dereference a NULL endpoint pointer and crash.

The weakness was shared by djnn as 1813. The advisory is shared at github.com. This vulnerability is known as CVE-2026-23679 since 01/14/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 318007 (Linux Distros Unpatched Vulnerability : CVE-2026-23679), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.0.30 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 578ab76b4c434f8b204137ab6d7310689c7a9704 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (318007). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• libusb

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.0.9
• 1.0.10
• 1.0.11
• 1.0.12
• 1.0.13
• 1.0.14
• 1.0.15
• 1.0.16
• 1.0.17
• 1.0.18
• 1.0.19
• 1.0.20
• 1.0.21
• 1.0.22
• 1.0.23
• 1.0.24
• 1.0.25
• 1.0.26
• 1.0.27
• 1.0.28
• 1.0.29

License

• open-source

Website

• Product: https://github.com/libusb/libusb/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion