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

High 7.8 EPSS 0.1% Linux kernel

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutex_unlock() may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly (unlike spinlocks and refcounts). [1][2] Use a kref to release the driver data to avoid use-after-free in mutex_unlock() when release() races with disconnect(). [1] a51749ab34d9 ("locking/mutex: Document that mutex_unlock() is non-atomic") [2] 2b9d9e0a9ba0 ("locking/mutex: Clarify that mutex_unlock(), and most other sleeping locks, can still use the lock object after it's unlocked")

CVE-2026-64341CVE identifier
7.8CVSS 3.1 base score (high)
0.1%EPSS: chance of exploitation in the next 30 days (higher than 2% of CVEs)
2026-07-25published

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

Check whether you run Linux kernel and which version (commands below).
Install the fixed version for your system: see “Patch it” below.
Reboot into the new kernel (uname -r to confirm); live patching (kpatch, Ubuntu Livepatch, SUSE kGraft/klp) can defer the reboot for some CVEs

Affected and fixed versions

Affected:

Linux Linux 946b960d13c15f050a3b848987aaca79f6a459b7 to before 9472acd56a020c93be4189d2dba9c743b9fc8039
Linux Linux 946b960d13c15f050a3b848987aaca79f6a459b7 to before 4e7d3c98fed73d3be84d3e146d8d9be0309e725b
Linux Linux 946b960d13c15f050a3b848987aaca79f6a459b7 to before 3c0a7b29ebb391d5f50b115e86f842b709195b08
Linux Linux 946b960d13c15f050a3b848987aaca79f6a459b7 to before 30ec3025b771511625375fb3fb959aea3b45fb0d
Linux Linux 946b960d13c15f050a3b848987aaca79f6a459b7 to before 71590982700fdeb39a37a500c877228b0140978e
Linux Linux 946b960d13c15f050a3b848987aaca79f6a459b7 to before c602254ba4c10f60a73cd99d147874f86a3f485c
Linux Linux 2.6.21

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Debian

sudo apt update
sudo apt install --only-upgrade linux-image-amd64

Ubuntu

sudo apt update
sudo apt install --only-upgrade linux-image-generic (or the installed flavour: linux-image-aws, -azure, -gcp, -virtual)

RHEL, AlmaLinux, Rocky, Oracle

sudo dnf upgrade --refresh kernel

Fedora

sudo dnf upgrade --refresh kernel

SUSE / openSUSE

sudo zypper refresh
sudo zypper update kernel-default

Amazon Linux

sudo dnf upgrade --releasever=latest kernel kernel6.12

Arch Linux

sudo pacman -Syu

Alpine

apk update && apk upgrade linux-lts linux-virt

FreeBSD

not Linux

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

Fix status in Linux distributions

Release	Package	Status	Fixed version / advisory
Debian 12	`linux`	not fixed yet
Debian 13	`linux`	fixed	`6.12.100-1`
Debian testing	`linux`	fixed	`7.1.4-1`
Debian 12	`linux-6.12`	fixed	`6.12.100-1~deb12u1`
Red Hat Enterprise Linux 9	`kernel`	affected
Red Hat Enterprise Linux 9	`kernel-rt`	affected
Red Hat Enterprise Linux 8	`kernel`	affected
Red Hat Enterprise Linux 8	`kernel-rt`	affected
Red Hat Enterprise Linux 7	`kernel`	affected
Red Hat Enterprise Linux 7	`kernel-rt`	affected
Red Hat Enterprise Linux 6	`kernel`	out of support scope
Red Hat Enterprise Linux 10	`kernel`	affected

From the Debian security tracker, Ubuntu CVE tracker and Red Hat Security Data API, refreshed every few hours.

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC. Always confirm with your vendor's advisory.