cxl/mbox: Break poison list loop on an empty payload
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ed83f7ca398b3798b82c1d5d1113011c0e5a2198 · fixed in 86771c105293ca26bfcc320b4f60d32c137b54aa; From ed83f7ca398b3798b82c1d5d1113011c0e5a2198 · fixed in 42eab80981f4d2ac820e253e80ecf92f8cd91f69; From ed83f7ca398b3798b82c1d5d1113011c0e5a2198 · fixed in 6ad491cef1a812cf7b53aa769cd8869516c47362; From ed83f7ca398b3798b82c1d5d1113011c0e5a2198 · fixed in e77594e0cea67ab1c2317a27aa77a744e26ad6a6; From ed83f7ca398b3798b82c1d5d1113011c0e5a2198 · fixed in 8b301c4afbce4bc3f94528441d8d5ce1366504ad
- Linux Linux
6.4
- KernelLinux
From 6.4.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6