CVE-2024-26761cxl/pci: Fix disabling memory if DVSEC CXL Range does not match a CFMWS window
- 5.5MediumCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% 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/pci: Fix disabling memory if DVSEC CXL Range does not match a CFMWS window The Linux CXL subsystem is built on the assumption that HPA == SPA. That is, the host physical address (HPA) the HDM decoder registers are programmed with are system physical addresses (SPA). During HDM decoder setup, the DVSEC CXL range registers (cxl-3.1, 8.1.3.8) are checked if the memory is enabled and the CXL range is in a HPA window that is described in a CFMWS structure of the CXL host bridge (cxl-3.1, 9.18.1.3). Now, if the HPA is not an SPA, the CXL range does not match a CFMWS window and the CXL memory range will be disabled then. The HDM decoder stops working which causes system memory being disabled and further a system hang during HDM decoder initialization, typically when a CXL enabled kernel boots. Prevent a system hang and do not disable the HDM decoder if the decoder's CXL range is not found in a CFMWS window. Note the change only fixes a hardware hang, but does not implement HPA/SPA translation. Support for this can be added in a follow on patch series.
Timeline
ID reserved
By Linux
- 44 days later
· 44 days later
Published
- 2 years later
· 2 years 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 34e37b4c432cd0f1842b352fde4b8878b4166888 – < 031217128990d7f0ab8c46db1afb3cf1e075fd29
- affected 34e37b4c432cd0f1842b352fde4b8878b4166888 – < 2cc1a530ab31c65b52daf3cb5d0883c8b614ea69
- affected 34e37b4c432cd0f1842b352fde4b8878b4166888 – < 3a3181a71935774bda2398451256d7441426420b
- affected 34e37b4c432cd0f1842b352fde4b8878b4166888 – < 0cab687205986491302cd2e440ef1d253031c221
- affected 5.19
- unaffected < 5.19
- unaffected 6.1.80 – ≤ 6.1.*
- unaffected 6.6.19 – ≤ 6.6.*
- unaffected 6.7.7 – ≤ 6.7.*
- unaffected 6.8 – ≤ *
References
References4
- https://git.kernel.org/stable/c/031217128990d7f0ab8c46db1afb3cf1e075fd29 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/2cc1a530ab31c65b52daf3cb5d0883c8b614ea69 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/3a3181a71935774bda2398451256d7441426420b (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/0cab687205986491302cd2e440ef1d253031c221 (opens in a new tab)x_transferred
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-2024-24023 (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-2024-26761)Record last updated .