cxl/mbox: Break poison list loop on an empty payload (CVE-2026-93097) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93097

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

Answer in brief

CVE-2026-93097 records a Unknown severity vulnerability in cxl/mbox: Break poison list loop on an empty payload. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=ed83f7ca398b3798b82c1d5d1113011c0e5a2198 <86771c105293ca26bfcc320b4f60d32c137b54aa \|\| >=ed83f7ca398b3798b82c1d5d1113011c0e5a2198 <42eab80981f4d2ac820e253e80ecf92f8cd91f69 \|\| >=ed83f7ca398b3798b82c1d5d1113011c0e5a2198 <6ad491cef1a812cf7b53aa769cd8869516c47362 \|\| >=ed83f7ca398b3798b82c1d5d1113011c0e5a2198 <e77594e0cea67ab1c2317a27aa77a744e26ad6a6 \|\| >=ed83f7ca398b3798b82c1d5d1113011c0e5a2198 <8b301c4afbce4bc3f94528441d8d5ce1366504ad	86771c105293ca26bfcc320b4f60d32c137b54aa, 42eab80981f4d2ac820e253e80ecf92f8cd91f69, 6ad491cef1a812cf7b53aa769cd8869516c47362, e77594e0cea67ab1c2317a27aa77a744e26ad6a6, 8b301c4afbce4bc3f94528441d8d5ce1366504ad
Linux/Linuxgeneric	6.4	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 86771c105293ca26bfcc320b4f60d32c137b54aa if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.