Strix
63.5K

CVE-2026-93097

Unknown

Last modified

CVE-2026-93097 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ed83f7ca398b3798b82c1d5d1113011c0e5a2198, < 86771c105293ca26bfcc320b4f60d32c137b54aa; >= ed83f7ca398b3798b82c1d5d1113011c0e5a2198, < 42eab80981f4d2ac820e253e80ecf92f8cd91f69; >= ed83f7ca398b3798b82c1d5d1113011c0e5a2198, < 6ad491cef1a812cf7b53aa769cd8869516c47362; >= ed83f7ca398b3798b82c1d5d1113011c0e5a2198, < e77594e0cea67ab1c2317a27aa77a744e26ad6a6; >= ed83f7ca398b3798b82c1d5d1113011c0e5a2198, < 8b301c4afbce4bc3f94528441d8d5ce1366504ad
LinuxLinux6.4

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93097?
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.
How severe is CVE-2026-93097?
Severity scoring for CVE-2026-93097 is pending analysis.
How do I fix CVE-2026-93097?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-93097?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST