CVE-2026-93186cxl/mbox: Clamp mailbox output allocation to the payload size
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: cxl/mbox: Clamp mailbox output allocation to the payload size CXL_MEM_SEND_COMMAND bounds the user's in.size to the mailbox payload size but leaves out.size unbounded, then cxl_mbox_cmd_ctor() calls kvzalloc(out.size). A large out.size drives a huge allocation, above INT_MAX it WARNs and taints, and with panic_on_warn=1 it panics. The transport __cxl_pci_mbox_send_cmd() already clamps the response copy to min(out.size, payload_size, device len), so the output buffer is never written beyond payload_size. Clamp the allocation to payload_size too, matching the RAW path.
Timeline
ID reserved
By Linux
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 583fa5e71caeb79e04e477e9837e2f7fa53b71e4 – < 123f6d154253939ce38f0ec0b6d1ba67f870e01f
- affected 583fa5e71caeb79e04e477e9837e2f7fa53b71e4 – < d2d40574b9b272ade32d0d77b140d990e7547f5f
- affected 583fa5e71caeb79e04e477e9837e2f7fa53b71e4 – < f5d2bbf0300f46307948864fbb97bce5097f4fe2
- affected 583fa5e71caeb79e04e477e9837e2f7fa53b71e4 – < 31d4841eca7c4b75751ca96d24339e19303337f2
- affected 583fa5e71caeb79e04e477e9837e2f7fa53b71e4 – < b4e11c731d6bee3b87315e055a1ca417c92dc1fc
- affected 583fa5e71caeb79e04e477e9837e2f7fa53b71e4 – < 8a13db9f899d149c3aab24abcb668121cfda5a4f
- affected 5.12
- unaffected < 5.12
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/123f6d154253939ce38f0ec0b6d1ba67f870e01f (opens in a new tab)
- https://git.kernel.org/stable/c/d2d40574b9b272ade32d0d77b140d990e7547f5f (opens in a new tab)
- https://git.kernel.org/stable/c/f5d2bbf0300f46307948864fbb97bce5097f4fe2 (opens in a new tab)
- https://git.kernel.org/stable/c/31d4841eca7c4b75751ca96d24339e19303337f2 (opens in a new tab)
- https://git.kernel.org/stable/c/b4e11c731d6bee3b87315e055a1ca417c92dc1fc (opens in a new tab)
- https://git.kernel.org/stable/c/8a13db9f899d149c3aab24abcb668121cfda5a4f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82294 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93186)Record last updated .