CVE-2026-43427: Linux kernel · usb: class: cdc-wdm: fix reordering issue in read code path
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e3c874b05901dc519054b5107d16620e6d2b5fea : update Linux kernel when convenient.
Data as of 6 Nov 2026, 15:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in e3c874b05901dc519054b5107d16620e6d2b5fea, c8fa96ed021923dae147bcd9f9205b8df7b82360, 638328ca9c17ae6511ad62198c57bae32ffa3c91 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: usb: class: cdc-wdm: fix reordering issue in read code path Quoting the bug report: Due to compiler optimization or CPU out-of-order execution, the desc->length update can be reordered before the memmove. If this happens, wdm_read() can see the new length and call copy_to_user() on uninitialized memory. This also violates LKMM data race rules [1]. Fix it by using WRITE_ONCE and memory barriers.
References
- git.kernel.org/stable/c/638328ca9c17ae6511ad62198c57bae32ffa3c91 (opens in a new tab)
- git.kernel.org/stable/c/170e8daca24da6edb4be82ab01abf44e87af387b (opens in a new tab)
- git.kernel.org/stable/c/c8fa96ed021923dae147bcd9f9205b8df7b82360 (opens in a new tab)
- git.kernel.org/stable/c/4ee3062bf2c9a722afef429826e8607eaf3fc6a0 (opens in a new tab)
- git.kernel.org/stable/c/276aef0fd2b92f41b920ac891c72cadeee957934 (opens in a new tab)
- git.kernel.org/stable/c/67ed312124bb1b61858778ac0b985b48961c862a (opens in a new tab)
- git.kernel.org/stable/c/e3c874b05901dc519054b5107d16620e6d2b5fea (opens in a new tab)
- git.kernel.org/stable/c/8df672bfe3ec2268c2636584202755898e547173 (opens in a new tab)