platform/x86/amd/pmc: Propagate SMU errors and validate S2D address
CVE-2026-81016 · published 11 Sept 2026
How serious is it
- Severity: high, CVSS score 7.7 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-81016?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d to < 85ef9d4c384c1d143c51580933674d94dba3b8d9, 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d to < 638e1ca5d4e2b4fdbb209db64926d013b34f3b79, 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d to < 8178f59d76570b152d836bde07f5997f15861f04, 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d to < 775d4cde1f9737796ce7d8393521e9e8c5b49891
- Linux Linux: 5.18
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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().
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/85ef9d4c384c1d143c51580933674d94dba3b8d9
- git.kernel.org/stable/c/638e1ca5d4e2b4fdbb209db64926d013b34f3b79
- git.kernel.org/stable/c/8178f59d76570b152d836bde07f5997f15861f04
- git.kernel.org/stable/c/775d4cde1f9737796ce7d8393521e9e8c5b49891
- git.kernel.org/stable/c/0225c1d637687b03726f00ac65b6def843d2c464
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON