CVE-2026-93097: cxl/mbox: Break poison list loop on an empty payload
cxl/mbox: Break poison list loop on an empty payload
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.157.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
In the CXL poison-list scan, break the loop when the device returns an empty payload (count == 0), even if CXL_POISON_FLAG_MORE is set, so the scan cannot loop indefinitely while holding poison.mutex.
Event History
Frequently Asked Questions
What conditions are required to trigger the hang?
A CXL device must repeatedly return a poison-list response with count equal to 0 while keeping CXL_POISON_FLAG_MORE set. This can occur with a malfunctioning or malicious device during a poison-list scan.
What is the operational impact if the issue is triggered?
The sysfs-triggered poison scan thread loops indefinitely while holding poison.mutex. Subsequent poison operations for that device are blocked.
Are systems without CXL poison-list scanning exposed?
The described hang occurs in the sysfs-triggered poison scan path. The provided information does not identify other affected paths.
How can I recognize an affected device or incident?
A poison scan can hang and poison operations on the same device can remain blocked. The triggering device behavior is repeated empty poison-list payloads with the MORE flag set.