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-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-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-64342 USB: iowarrior: fix use-after-free on disconnect

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 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-64340 USB: legousbtower: fix use-after-free on disconnect race

In the Linux kernel, the following vulnerability has been resolved: USB: legousbtower: 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 U...

CVE-2026-64340

The CVE-2026-64340 entry concerns the Linux kernel USB legousbtower driver. A use-after-free can occur because mutex_unlock() may access the mutex object after the lock is released, which can mismanage object lifetimes during disconnect races. The documented fix is to release the driver data usin...

EUVD-2026-48878

In the Linux kernel, the following vulnerability has been resolved: USB: serial: digiacceleport: fix hard lockup on disconnect If submitting the OOB write urb fails persistently e.g if the device is being disconnected the driver would loop indefinitely with interrupts disabled. Check for urb...

EUVD-2026-48869

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921/mt7925: fix NULL dereference in CSA beacon This patch is based on a BUG as reported by Bongani Hlope at https://lore.kernel.org/all/[email protected]/ When a channel-switch...

CVE-2026-64311 crypto: loongson - Remove broken and unused loongson-rng

In the Linux kernel, the following vulnerability has been resolved: crypto: loongson - Remove broken and unused loongson-rng The loongson-rng rngalg has several vulnerabilities, including not providing forward security, and a use-after-free bug due to the use of waitforcompletioninterruptible...

CVE-2026-64311

The CVE concerns the Linux kernel: crypto: loongson - Remove broken and unused loongson-rng. The loongson-rng rng_alg reportedly has forward-security issues and a use-after-free bug linked to wait_for_completion_interruptible(), and the rng_alg framework is largely unused in-kernel. The advisory ...

CVE-2026-64309 crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT)

In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctlSNPCOMMIT Sashiko notes: if SEV initialization fails and KVM is actively running normal VMs, could a userspace process trigger this code path via /dev/sev ioctls e.g., SEVPDHGEN and ze...

EUVD-2026-49020

In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctlSNPVLEKLOAD Sashiko notes: if SEV initialization fails and KVM is actively running normal VMs, could a userspace process trigger this code path via /dev/sev ioctls e.g., SEVPDHGEN and...

CVE-2026-64275

CVE-2026-64275 affects the Linux kernel elan_i2c driver. The fault is division by zero when x_traces/y_traces are zero and an unsigned underflow in width calculation; patch adds non-zero checks and clamps width to >=0, with safe defaults (1) to ensure probe/sysfs nodes work and recovery firmwa...

CVE-2026-64273

In the Linux kernel, the following vulnerability has been resolved: Input: iforce - bound the device-reported force-feedback effect index iforceprocesspacket handles a status report packet id 0x02 by taking a force-feedback effect index straight from the device wire and using it to address the...

CVE-2026-64271 Input: touchwin - reset the packet index on every complete packet

In the Linux kernel, the following vulnerability has been resolved: Input: touchwin - reset the packet index on every complete packet twinterrupt accumulates each non-zero serial byte into a fixed three-byte buffer with a running index that is only reset once a full packet has been received and t...