CVE-2025-38252
Last modified
CVE-2025-38252 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.15, < 6.15.5 | — |
| Linux | Linux Kernel | 6.16 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38252?
How severe is CVE-2025-38252?
How do I fix CVE-2025-38252?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38247In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38248In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38249In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-3825A vulnerability, which was classified as problematic, has be…4.1
- CVE-2025-38250In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38251In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38253In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38254In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38255In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38256In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38257In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38258In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38252?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
