Description
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")
Published: 2026-07-25
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The iowarrior USB driver in the Linux kernel contains a race condition that causes a use‑after‑free when the driver’s release path races with a device disconnect. The mutex unlocking code can still reference the freed memory, leading to memory corruption. An attacker that can trigger a USB disconnect while the driver is being released may force a kernel crash, potentially allowing escalation or denial of service.

Affected Systems

All Linux kernels that lack commit 3c0a7b29ebb391d5f50b115e86f842b709195b08 are affected. Vulnerable versions include kernel 2.6.21 rc1 through rc7, 7.2 rc1, 7.2 rc2, and any generic Linux kernels that have not yet incorporated the fix. The patch replaces the mutex unlocking with a reference counter (kref).

Risk and Exploitability

The CVSS score of 7.8 indicates moderate‑to‑high severity. EPSS is reported as < 1%, showing a very low likelihood of exploitation in the wild, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a local user or process that can insert or remove a USB device to trigger the race. While no publicly documented exploit exists, the crash risk warrants prompt patching.

Generated by OpenCVE AI on September 3, 2026 at 21:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a release that includes commit 3c0a7b29ebb391d5f50b115e86f842b709195b08, which replaces the mutex unlocking with a reference counter.
  • If an immediate kernel upgrade is not possible, unload or disable the iowarrior USB driver so the vulnerable code path is not exercised.
  • Continue monitoring kernel logs (dmesg, syslog) for memory corruption or panic messages and enable crash dumps to capture additional diagnostic information.

Generated by OpenCVE AI on September 3, 2026 at 21:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4724-1 linux-6.12 new package
Debian DSA Debian DSA DSA-6405-1 linux security update
History

Thu, 03 Sep 2026 16:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CPEs cpe:2.3:o:linux:linux_kernel:2.6.21:-:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:2.6.21:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:2.6.21:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:2.6.21:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:2.6.21:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:2.6.21:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:2.6.21:rc7:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.2:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.2:rc2:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Tue, 04 Aug 2026 15:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Thu, 30 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate


Sun, 26 Jul 2026 02:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Sat, 25 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
Description 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")
Title USB: iowarrior: fix use-after-free on disconnect race
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T04:53:44.970Z

Reserved: 2026-07-19T15:36:31.781Z

Link: CVE-2026-64341

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2026-07-25T10:17:16.117

Modified: 2026-09-03T16:01:49.520

Link: CVE-2026-64341

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-25T00:00:00Z

Links: CVE-2026-64341 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-03T22:00:13Z

Weaknesses