CVE-2024-26761

cxl/pci: Fix disabling memory if DVSEC CXL Range does not match a CFMWS window

MEDIUM
5.5
CVSS Score
Published: April 3, 2024 at 05:00 PM UTC
Updated: June 17, 2026 at 07:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.19 ≤ v < 6.1.805.19 ≤ v < 6.6.195.19 ≤ v < 6.7.75.19 ≤ v < 6.86.2 ≤ v < 6.6.196.7 ≤ v < 6.7.734e37b4c432cd0f1842b352fde4b8878b41668886.8 rc16.8 rc26.8 rc36.8 rc46.8 rc5
Vendor states this is fixed in 031217128990d7f0ab8c46db1afb3cf1e075fd29 (fixed)
Vendor states this is fixed in 0cab687205986491302cd2e440ef1d253031c221 (fixed)
Vendor states this is fixed in 2cc1a530ab31c65b52daf3cb5d0883c8b614ea69 (fixed)
Vendor states this is fixed in 3a3181a71935774bda2398451256d7441426420b (fixed)
Vendor states this is fixed in 5.19 (unaffected)
Vendor states this is fixed in 6.1.80 (unaffected)
Vendor states this is fixed in 6.6.19 (unaffected)
Vendor states this is fixed in 6.7.7 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/031217128990d7f0ab8c46db1afb3cf1e075fd29
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0cab687205986491302cd2e440ef1d253031c221
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2cc1a530ab31c65b52daf3cb5d0883c8b614ea69
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3a3181a71935774bda2398451256d7441426420b

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card