CVE-2024-26762: cxl/pci: Skip to handle RAS errors if CXL.mem device is detached
In the Linux kernel, the following vulnerability has been resolved:
cxl/pci: Skip to handle RAS errors if CXL.mem device is detached
The PCI AER model is an awkward fit for CXL error handling. While the
expectation is that a PCI device can escalate to link reset to recover
from an AER event, the same reset on CXL amounts to a surprise memory
hotplug of massive amounts of memory.
At present, the CXL error handler attempts some optimistic error
handling to unbind the device from the cxl_mem driver after reaping some
RAS register values. This results in a "hopeful" attempt to unplug the
memory, but there is no guarantee that will succeed.
A subsequent AER notification after the memdev unbind event can no
longer assume the registers are mapped. Check for memdev bind before
reaping status register values to avoid crashes of the form:
BUG: unable to handle page fault for address: ffa00000195e9100
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
[...]
RIP: 0010:__cxl_handle_ras+0x30/0x110 [cxl_core]
[...]
Call Trace:
<TASK>
? __die+0x24/0x70
? page_fault_oops+0x82/0x160
? kernelmode_fixup_or_oops+0x84/0x110
? exc_page_fault+0x113/0x170
? asm_exc_page_fault+0x26/0x30
? __pfx_dpc_reset_link+0x10/0x10
? __cxl_handle_ras+0x30/0x110 [cxl_core]
? find_cxl_port+0x59/0x80 [cxl_core]
cxl_handle_rp_ras+0xbc/0xd0 [cxl_core]
cxl_error_detected+0x6c/0xf0 [cxl_core]
report_error_detected+0xc7/0x1c0
pci_walk_bus+0x73/0x90
pcie_do_recovery+0x23f/0x330
Longer term, the unbind and PCI_ERS_RESULT_DISCONNECT behavior might
need to be replaced with a new PCI_ERS_RESULT_PANIC.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw can crash systems using CXL memory when another PCI error arrives after a CXL.mem device detaches. The handler may access registers that are no longer mapped. This threatens system stability and potentially broader security properties, but the supplied sources provide no evidence of active exploitation.
Executive priority
Treat as a high-priority reliability and security update for CXL-enabled infrastructure. Patch exposed systems during the next urgent maintenance window, accelerating systems with frequent hardware errors or memory hotplug activity. Conventional servers without CXL.mem hardware are less likely to be exposed.
Technical view
After cxl_mem unbind, a subsequent PCI AER notification may invoke CXL RAS handling and read unmapped status registers, causing a kernel page fault. The fix checks whether the memory device remains bound before accessing those registers. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction.
Likely exposure
Exposure is limited to Linux systems using affected kernels with CXL.mem hardware and the relevant detach, unbind, and subsequent AER error sequence. The record lists Linux 6.7 through 6.7.7 and 6.8 as affected. Distribution backports may change actual status.
Exploitation context
The vulnerability requires local, low-privileged access according to the CVSS vector, plus a specific CXL and PCI error-handling state. It is not listed in KEV, and the supplied sources do not establish public or active exploitation. Practical reachability may depend heavily on hardware and local system controls.
Researcher notes
The vulnerable condition is a stale register-access assumption after memdev unbind. The source describes a supervisor-mode page fault in __cxl_handle_ras during PCIe recovery. The immediate correction adds a bind-state check; the record also notes that longer-term CXL recovery behavior may require redesign. No CWE was supplied.
Mitigation direction
Upgrade to a vendor-supported kernel containing the referenced stable fix or an equivalent backport.
Check Linux distribution advisories for package-specific fixed versions and reboot requirements.
Prioritize CXL.mem hosts where unbind, hotplug, or PCI AER events can occur.
Restrict unnecessary local access while affected systems await remediation.
Validation and detection
Inventory kernel versions and identify hosts using CXL.mem devices.
Confirm the installed kernel package includes either referenced fix or an equivalent vendor backport.
Review kernel logs for CXL RAS faults, page faults, or crashes following device detach events.
Validate normal CXL error handling after upgrading, using approved non-destructive operational tests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-26762 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.