LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel CXL memory initialization bug. On affected CXL-enabled systems, the kernel can disable a memory decoder when address windows do not match, leading to disabled system memory and a boot-time hang. The sources describe an availability issue, not data theft or remote compromise.

Executive priority

Treat this as targeted availability risk for CXL infrastructure. It is not currently evidenced as exploited, but affected systems may fail to boot reliably. Prioritize remediation for production servers using CXL memory or validating CXL deployments.

Technical view

During CXL HDM decoder setup, Linux checked DVSEC CXL range registers against CFMWS windows assuming host physical addresses equal system physical addresses. When they differ, the range may not match, causing the decoder to be disabled and the system to hang. The fix avoids disabling the HDM decoder in that mismatch case.

Likely exposure

Exposure appears limited to Linux systems using CXL memory hardware and kernels in the affected ranges. The source bundle lists Linux kernel 5.19-era code and stable fixes around 6.1.80, 6.6.19, 6.7.7, and 6.8. Non-CXL systems are unlikely to be practically affected.

Exploitation context

No active exploitation is cited, and this CVE is not marked KEV in the supplied bundle. The described failure is a hardware and kernel initialization hang, typically when a CXL-enabled kernel boots, rather than a remotely triggerable exploit path.

Researcher notes

The patch prevents the hang but explicitly does not implement HPA-to-SPA translation. Evidence is incomplete for CVSS, CWE, exploitability, and distribution-specific package status. Validation should focus on kernel branch, CXL hardware presence, and whether the stable fix was backported.

Mitigation direction

  • Identify Linux hosts using CXL memory hardware or CXL-enabled kernels.
  • Update to a kernel containing the referenced stable fixes.
  • Check distribution vendor advisories for backported kernel packages.
  • Prioritize systems where boot availability is operationally critical.

Validation and detection

  • Inventory kernel versions on CXL-capable servers.
  • Confirm whether CXL memory devices are present and enabled.
  • Review boot logs for CXL HDM decoder initialization failures or hangs.
  • Verify installed kernels include the referenced upstream stable commits.
Prepared
Confidence
medium
Sources
6

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-26761 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux34e37b4c432cd0f1842b352fde4b8878b4166888, 34e37b4c432cd0f1842b352fde4b8878b4166888, 34e37b4c432cd0f1842b352fde4b8878b4166888, 34e37b4c432cd0f1842b352fde4b8878b4166888unaffected
LinuxLinux5.19, 0, 6.1.80, 6.6.19, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.