CVE-2026-81016

platform/x86/amd/pmc: Propagate SMU errors and validate S2D address

HIGH
7.7
CVSS Score
Published: September 11, 2026 at 07:43 PM UTC
Updated: October 30, 2026 at 01:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.7
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Propagate SMU errors and validate S2D address amd_stb_s2d_init() discards the return value of several S2D SMU commands. When the SMU refuses a command (e.g. "SMU cmd failed. err: 0xff") the failure is only noticed indirectly - if at all - and reported as -EIO, masking the real error. More seriously, the S2D_PHYS_ADDR_LOW/HIGH return values are ignored, so on failure phys_addr_low/hi are left uninitialised and the assembled address is passed straight to devm_ioremap(). When the SMU leaves them at zero this maps physical address 0 and trips the ioremap-on-RAM warning: amd_pmc AMDI000B:00: SMU cmd failed. err: 0xff ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff WARNING: CPU: 13 PID: 4592 at arch/x86/mm/ioremap.c:... Check the return value of each SMU command and propagate it, and reject a zero physical address before calling devm_ioremap().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d5.18
Vendor states this is fixed in 0225c1d637687b03726f00ac65b6def843d2c464 (fixed)
Vendor states this is fixed in 638e1ca5d4e2b4fdbb209db64926d013b34f3b79 (fixed)
Vendor states this is fixed in 775d4cde1f9737796ce7d8393521e9e8c5b49891 (fixed)
Vendor states this is fixed in 8178f59d76570b152d836bde07f5997f15861f04 (fixed)
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 6.12.112 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.7HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card