GHSA-X7W4-F354-Q3XF
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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": [],
"aliases": [
"CVE-2026-93097"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:03Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncxl/mbox: Break poison list loop on an empty payload\n\nA device that returns count == 0 with CXL_POISON_FLAG_MORE set on every\niteration never advances nr_records, so the max_errors guard never\ntrips and the do/while loops forever while holding poison.mutex. That\nhangs the sysfs-triggered scan thread and blocks all subsequent poison\noperations on the device. The existing \"Protect against an uncleared\n_FLAG_MORE\" guard was intended to bound a misbehaving device but does\nnot cover the count == 0 case.\n\nStop the loop on an empty payload so a malfunctioning or malicious\ndevice cannot wedge the poison scan.",
"id": "GHSA-x7w4-f354-q3xf",
"modified": "2026-09-17T18:32:10Z",
"published": "2026-09-17T18:32:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93097"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/42eab80981f4d2ac820e253e80ecf92f8cd91f69"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6ad491cef1a812cf7b53aa769cd8869516c47362"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/86771c105293ca26bfcc320b4f60d32c137b54aa"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8b301c4afbce4bc3f94528441d8d5ce1366504ad"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e77594e0cea67ab1c2317a27aa77a744e26ad6a6"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.