CVE-2026-93097

cxl/mbox: Break poison list loop on an empty payload

Published Sep 17, 2026 CVSS n/a EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability stems from an infinite loop in the Linux kernel’s CXL poison scan routine. A device that repeatedly reports a payload count of zero while setting the CXL_POISON_FLAG_MORE flag causes the loop to never advance the record counter, never reach the maximum error guard, and hold the poison mutex indefinitely. This lock remains inside the sysfs-triggered scan thread, blocking all subsequent poison operations on the device and effectively hanging the related subsystem.

Affected Systems

Any Linux distribution that includes the CXL mailbox (cxl/mbox) component of the kernel is potentially affected. The vendor name is Linux and the product is the Linux kernel; specific version information is not provided in the advisories.

Risk and Exploitability

The EPSS score is reported as less than 1 %, indicating a very low probability of widespread exploitation at this time. The vulnerability is not listed in the CISA KEV catalog, and no CVSS score is supplied. Based on the description, an attacker would need to interact with a CXL device that can return the anomalous payload; this could occur locally or via a compromised device. The impact is a denial of service through a hung scan thread and blocked poison operations. No known workaround is specified.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest security update for the Linux kernel that incorporates the fix for the infinite loop in cxl/mbox.
  • Reboot or reload the kernel so the patched driver logic is active and the poison mutex no longer hangs the scan thread.
  • Verify CXL devices return normal payload counts and, if a misbehaving device is detected, consider removing the device or disabling the CXL subsystem until a patched kernel is available.

Generated by OpenCVE AI on September 19, 2026 at 07:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4817-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6528-1 linux security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9022-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9023-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9039-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9183-1 Linux kernel (FIPS) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-674
Type Values Removed Values Added
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.
Title cxl/mbox: Break poison list loop on an empty payload
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 9:05 AM
Reserved
Sep 17, 2026, 4:02 PM
Status
Received
Published
Sep 17, 2026, 5:18 PM
Modified
Oct 19, 2026, 10:16 AM