LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38252: cxl/ras: Fix CPER handler device confusion

In the Linux kernel, the following vulnerability has been resolved: cxl/ras: Fix CPER handler device confusion By inspection, cxl_cper_handle_prot_err() is making a series of fragile assumptions that can lead to crashes: 1/ It assumes that endpoints identified in the record are a CXL-type-3 device, nothing guarantees that. 2/ It assumes that the device is bound to the cxl_pci driver, nothing guarantees that. 3/ Minor, it holds the device lock over the switch-port tracing for no reason as the trace is 100% generated from data in the record. Correct those by checking that the PCIe endpoint parents a cxl_memdev before assuming the format of the driver data, and move the lock to where it is required. Consequently this also makes the implementation ready for CXL accelerators that are not bound to cxl_pci.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux CXL error-handling flaw can confuse an unexpected PCIe endpoint for a CXL memory device and crash the kernel. The supplied CVSS score is 7.8, requiring local, low-privileged access. Systems using affected kernels with CXL hardware or related error-record processing deserve prompt review.

Executive priority

Prioritize remediation for CXL-capable systems running potentially affected kernels, especially shared hosts with untrusted local users. For systems without CXL exposure, validate applicability before emergency action. There is no supplied evidence of active exploitation, but a kernel crash risk and high CVSS score justify timely patching.

Technical view

The CXL RAS CPER protocol-error handler assumed a reported endpoint was a CXL Type-3 device bound to cxl_pci, then interpreted its driver data accordingly. The correction verifies that the endpoint parents a cxl_memdev and narrows device-lock scope. The source states these fragile assumptions can cause crashes.

Likely exposure

The bundle identifies Linux 6.15 through the listed 6.15.5 and 6.16 entries as affected, but its version representation is ambiguous. Practical exposure likely requires the vulnerable kernel handler and relevant CXL/CPER processing. Confirm exact distribution backports and hardware configuration with the kernel vendor.

Exploitation context

CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. CVSS describes a local, low-complexity attack requiring low privileges and no user interaction. The sources do not explain how an attacker would trigger or control the necessary error record, so real-world exploitability remains uncertain.

Researcher notes

The disclosed root cause is device-type and driver-binding confusion in cxl_cper_handle_prot_err(), plus overly broad locking. The fix validates the cxl_memdev relationship before accessing assumed driver data and prepares for non-cxl_pci CXL accelerators. No CWE, proof of concept, trigger details, or confirmed exploitation is supplied.

Mitigation direction

  • Install a vendor kernel containing the applicable referenced stable fix or documented backport.
  • Check distribution advisories for corrected package versions; upstream version entries alone are ambiguous.
  • Prioritize CXL-enabled systems and hosts permitting untrusted local access.
  • Restrict unnecessary local accounts while patching, treating this as interim risk reduction.

Validation and detection

  • Record each host's running kernel build and whether CXL devices or related error handling are present.
  • Confirm the kernel package includes an applicable referenced commit or vendor-confirmed backport.
  • Verify the handler checks for a parent cxl_memdev before interpreting driver data.
  • Review kernel crash records for failures associated with CXL RAS protocol-error handling.
Prepared
Confidence
medium
Sources
4

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-2025-38252 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38252Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux36f257e3b0ba904f5a4e7fa8dafaa60e88cdd28c, 36f257e3b0ba904f5a4e7fa8dafaa60e88cdd28cunaffected
LinuxLinux6.15, 0, 6.15.5, 6.16affected
Weakness

CWE details

No CWE listed

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