CVE-2026-93097: Linux kernel · cxl/mbox: Break poison list loop on an empty payload
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e77594e0cea67ab1c2317a27aa77a744e26ad6a6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e77594e0cea67ab1c2317a27aa77a744e26ad6a6, 86771c105293ca26bfcc320b4f60d32c137b54aa, 42eab80981f4d2ac820e253e80ecf92f8cd91f69 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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: cxl/mbox: Break poison list loop on an empty payload A device that returns count == 0 with CXL_POISON_FLAG_MORE set on every iteration never advances nr_records, so the max_errors guard never trips and the do/while loops forever while holding poison.mutex. That hangs the sysfs-triggered scan thread and blocks all subsequent poison operations on the device. The existing "Protect against an uncleared _FLAG_MORE" guard was intended to bound a misbehaving device but does not cover the count == 0 case. Stop the loop on an empty payload so a malfunctioning or malicious device cannot wedge the poison scan.
References
- git.kernel.org/stable/c/86771c105293ca26bfcc320b4f60d32c137b54aa (opens in a new tab)
- git.kernel.org/stable/c/42eab80981f4d2ac820e253e80ecf92f8cd91f69 (opens in a new tab)
- git.kernel.org/stable/c/6ad491cef1a812cf7b53aa769cd8869516c47362 (opens in a new tab)
- git.kernel.org/stable/c/e77594e0cea67ab1c2317a27aa77a744e26ad6a6 (opens in a new tab)
- git.kernel.org/stable/c/8b301c4afbce4bc3f94528441d8d5ce1366504ad (opens in a new tab)