CVE-2026-64347
Last modified
CVE-2026-64347 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: composite: fix dead empty check in the USB_DT_OTG handler The OTG branch of composite_setup() falls back to the first configuration when none is selected: if (cdev->config) config = cdev->config; else config = list_first_entry(&cdev->configs, struct usb_configuration, list); if (!config) goto done; ... memcpy(req->buf, config->descriptors[0], value); list_first_entry() never returns NULL. On an empty list it returns container_of() of the list head. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: composite: fix dead empty check in the USB_DT_OTG handler The OTG branch of composite_setup() falls back to the first configuration when none is selected: if (cdev->config) config = cdev->config; else config = list_first_entry(&cdev->configs, struct usb_configuration, list); if (!config) goto done; ... memcpy(req->buf, config->descriptors[0], value); list_first_entry() never returns NULL. On an empty list it returns container_of() of the list head. So the "if (!config)" check is dead. When cdev->configs is empty, config points at the head inside struct usb_composite_dev. config->descriptors[0] reads whatever sits at that offset. The memcpy copies up to w_length bytes of it into the response buffer. cdev->configs can be empty in two cases. One is a teardown race on gadget unbind with a control transfer in flight. The other is a driver that sets is_otg before it adds a config. A reproducer that holds cdev->configs empty triggers a KASAN fault in this branch. Use list_first_entry_or_null() so the existing check does its job.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.3, < 5.10.261 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.212 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.178 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 | — |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 | — |
| Linux | Linux Kernel | 7.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64347?
How severe is CVE-2026-64347?
How do I fix CVE-2026-64347?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64341In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64342In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64343In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64344In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64345In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64346In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64348In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64349In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64350In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64351In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64352In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64353In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64347?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
