Skip to content
Heist/ feed
Back to feed
HighFix available

cxl/ras: Fix CPER handler device confusion

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.15.5
CVEs
CVE-2025-38252
Confirmed fixed CVEs
Not specified
Updated in this feed
7 Nov 2026, 11:39 UTC · Revision 1

Source evidence

cxl/ras: Fix CPER handler device confusion

core-osv · Original source

Published 9 Jul 2025, 10:42 UTC

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.

osv:CVE-2025-38252

Kernel

Fixed versions: 6.15.5

Complete source record
{
  "id": "d5632e2f47f4072db09f5a8d1f0621715e8ec548c4a0051515d8947a2218e120",
  "url": "https://osv.dev/vulnerability/CVE-2025-38252",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "cxl/ras: Fix CPER handler device confusion",
    "summary": "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.",
    "evidence": "osv:CVE-2025-38252",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.15.5",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2025-38252",
      "aliases": [
        "CVE-2025-38252"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "36f257e3b0ba904f5a4e7fa8dafaa60e88cdd28c"
                },
                {
                  "fixed": "4bcb8dd36e9e3fad6c22862ac5b6993df838309b"
                },
                {
                  "fixed": "3c70ec71abdaf4e4fa48cd8fdfbbd864d78235a8"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38252.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.15.0"
                },
                {
                  "fixed": "6.15.5"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38252.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:50.938930948Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/3c70ec71abdaf4e4fa48cd8fdfbbd864d78235a8",
        "https://git.kernel.org/stable/c/4bcb8dd36e9e3fad6c22862ac5b6993df838309b",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38252.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-38252",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38252.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-38252",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 519155,
  "published_at": "2025-07-09T10:42:31.477+00:00"
}