CVE-2026-64348 usb: free iso schedules on failed submit

In the Linux kernel, the following vulnerability has been resolved: usb: free iso schedules on failed submit EHCI and FOTG210 isochronous submits build an ehciisosched before linking the URB to the endpoint queue, and keep the staged schedule in urb-hcpriv until isostreamschedule and the link...

CVE-2026-64347 usb: gadget: composite: fix dead empty check in the USB_DT_OTG handler

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: composite: fix dead empty check in the USBDTOTG handler The OTG branch of compositesetup falls back to the first configuration when none is selected: if cdev-config config = cdev-config; else config =...

CVE-2026-64346

Summary: CVE-2026-64346 affects the Linux kernel USB gadget udc path. A race condition can occur when the udc (managing gadget state) is freed by usb_del_gadget() while gadget_match_driver() may still access the freed udc (e.g., via configfs). This Use-After-Free can trigger a NULL pointer derefe...

EUVD-2026-48890

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: Fix use-after-free in gadgetmatchdriver The udc structure acts as the management structure for the gadget, but their lifecycles are decoupled. A race condition exists where usbdelgadget frees the udc memory e.g....

CVE-2026-64345

The CVE-2026-64345 issue affects the Linux kernel USB gadget f_printer driver. printer_open() increments dev->kref even when an open fails with -EBUSY, causing a reference leak because VFS does not call ->release() for failed opens. The fix moves the kref_get() into the successful-open path...

EUVD-2026-48889

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: fprinter: take kref only for successful open printeropen returns -EBUSY when the character device is already open, but it increments dev-kref regardless of the return value. VFS does not call -release for a failed...

CVE-2026-64345 usb: gadget: f_printer: take kref only for successful open

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: fprinter: take kref only for successful open printeropen returns -EBUSY when the character device is already open, but it increments dev-kref regardless of the return value. VFS does not call -release for a failed...

CVE-2026-64345 usb: gadget: f_printer: take kref only for successful open

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: fprinter: take kref only for successful open printeropen returns -EBUSY when the character device is already open, but it increments dev-kref regardless of the return value. VFS does not call -release for a failed...

CVE-2026-64346

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: Fix use-after-free in gadgetmatchdriver The udc structure acts as the management structure for the gadget, but their lifecycles are decoupled. A race condition exists where usbdelgadget frees the udc memory e.g....

EUVD-2026-48888

In the Linux kernel, the following vulnerability has been resolved: USB: idmouse: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use a...

CVE-2026-64344

CVE-2026-64344 tracks a Linux kernel USB idmouse driver use‑after‑free on disconnect race. The root cause: mutex_unlock() may touch the mutex after unlocking, risking lifetime management problems; the fix uses a kref to release driver data to avoid use‑after‑free when release() races with disconn...

CVE-2026-64344 USB: idmouse: fix use-after-free on disconnect race

In the Linux kernel, the following vulnerability has been resolved: USB: idmouse: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use a...

CVE-2026-64343

The CVE-2026-64343 issue is in the Linux kernel USB driver stack (ldusb). The vulnerability arises from a use-after-free race on disconnect where mutex_unlock() can access the mutex structure after the lock is released, risking lifetime management of objects. The documented fix introduces a kref-...

CVE-2026-64343 USB: ldusb: fix use-after-free on disconnect race

In the Linux kernel, the following vulnerability has been resolved: USB: ldusb: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use a kr...

CVE-2026-64342

The CVE-2026-64342 issue concerns the Linux kernel USB iowarrior driver. A use-after-free is triggered because submitted write URBs are not stopped on close(), and are not unconditionally halted on disconnect, allowing a completion handler to access freed resources. Multiple vendor advisories (Re...

EUVD-2026-48886

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

EUVD-2026-48887

In the Linux kernel, the following vulnerability has been resolved: USB: ldusb: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use a kr...

EUVD-2026-48885

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use ...

CVE-2026-64341 USB: iowarrior: fix use-after-free on disconnect race

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use ...

CVE-2026-64341

In CVE-2026-64341, the Linux kernel USB iowarrior driver fix addresses a use-after-free race on disconnect. The issue: mutex_unlock() can access the mutex structure after unlocking, potentially ending object lifetime management incorrectly. The mitigation: release the driver data using a kref to ...