CVE-2026-64346 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, as well as users of Linux-based systems, should be aware of this vulnerability and take steps to mitigate it. This includes reviewing Linux kernel versions, applying patches, and monitoring for future updates related to this vulnerability.

Technical summary

The vulnerability is caused by a race condition between the usb_del_gadget function and the gadget_match_driver function. The usb_del_gadget function frees the udc memory, while the gadget_match_driver function accesses the freed memory, leading to a Use-After-Free vulnerability. The patch introduces a new usb_gadget_release routine to ensure the udc structure remains allocated until the gadget is released.

Defensive priority

High

Recommended defensive actions

• Apply the patch to the Linux kernel to fix the vulnerability
• Use a Linux kernel version that has the patch applied
• Monitor Linux kernel updates for future patches related to this vulnerability
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was discovered and patched in the Linux kernel. The patch introduces a new usb_gadget_release routine to ensure the udc structure remains allocated until the gadget is released. Evidence is limited to CVE and NVD details. Defenders should verify Linux kernel versions, review configfs and USB gadget interactions, and monitor for related updates.

Official resources