cxl/ras: Fix CPER handler device confusion
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s CXL RAS CPER handler makes unsafe assumptions about the device identified in an error record. Processing a record that identifies an endpoint that is not a CXL type-3 device or is not bound to the cxl_pci driver can cause a crash. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with the affected CXL RAS CPER handler should check their deployments; affected versions are not specified.