The vulnerability resides in the Linux kernel’s handling of AMD Performance Monitoring Counters on x86 systems. During the initialization of the S2D interface, the function discards return values from many SMU commands, masking failures as a generic I/O error. More critically, the function ignores the low and high parts of the address returned by the SMU, so on failure these fields remain uninitialised and the assembled address is passed straight to devm_ioremap(). When the SMU leaves them at zero this maps physical address 0 and triggers an ioremap-on-RAM warning or result in undefined behaviour, while the real error source is concealed, hampering troubleshooting.

The Linux kernel, specifically the AMD Performance Monitoring Counters (PMC) driver on x86, is affected. All Linux kernel releases are covered by the provided CPE string. AMD CPUs with the PMU subsystem enabled are therefore the relevant platforms.

The CVSS score of 4.1 indicates low severity and the EPSS score is <1%, implying a low probability of exploitation. The vulnerability requires local kernel code execution to trigger the problematic path, making remote exploitation unlikely. It is not listed in the CISA KEV catalog, so there are currently no publicly documented exploits. The risk is limited to systems where the vulnerable kernel is deployed and the AMD PMU driver is active, and the exploitability is constrained to users who can load kernel modules or otherwise manipulate kernel memory.