CVE-2026-81016
platform/x86/amd/pmc: Propagate SMU errors and validate S2D address
Reported by linux · Published September 11, 2026
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().
EPSS 0.19% · 8.3th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | 85ef9d4c384c1d143c51580933674d94dba3b8d9, 8178f59d76570b152d836bde07f5997f15861f04, 775d4cde1f9737796ce7d8393521e9e8c5b49891, 646cdcc6c7594d8ad81577b2cb05276a927edc28, 638e1ca5d4e2b4fdbb209db64926d013b34f3b79, 0225c1d637687b03726f00ac65b6def843d2c464 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d, 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d, 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d |
| Linux | Linux | 5.18, 0, 6.1.191 |
| Linux | Linux | 7.3, 0, 6.1.191 |
| linux | linux_kernel | 5.18, 5.18, 5.18 |
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (13 in total, the first dated here)
- Sep 12, 2026 Coalition ESS Score
- Oct 30, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-81016
vulnetix vdb fixes CVE-2026-81016
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-81016/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart