CVE-2026-81016platform/x86/amd/pmc: Propagate SMU errors and validate S2D address
- 7.7HighCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
- 16 days later
· 16 days later
Published
- 49 days later
· 49 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.7 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.7 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 92% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.7.
Affected products
- affected 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d – < 646cdcc6c7594d8ad81577b2cb05276a927edc28
- affected 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d – < 85ef9d4c384c1d143c51580933674d94dba3b8d9
- affected 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d – < 638e1ca5d4e2b4fdbb209db64926d013b34f3b79
- affected 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d – < 8178f59d76570b152d836bde07f5997f15861f04
- affected 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d – < 775d4cde1f9737796ce7d8393521e9e8c5b49891
- affected 3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d – < 0225c1d637687b03726f00ac65b6def843d2c464
- affected 5.18
- unaffected < 5.18
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.50 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/646cdcc6c7594d8ad81577b2cb05276a927edc28 (opens in a new tab)
- https://git.kernel.org/stable/c/85ef9d4c384c1d143c51580933674d94dba3b8d9 (opens in a new tab)
- https://git.kernel.org/stable/c/638e1ca5d4e2b4fdbb209db64926d013b34f3b79 (opens in a new tab)
- https://git.kernel.org/stable/c/8178f59d76570b152d836bde07f5997f15861f04 (opens in a new tab)
- https://git.kernel.org/stable/c/775d4cde1f9737796ce7d8393521e9e8c5b49891 (opens in a new tab)
- https://git.kernel.org/stable/c/0225c1d637687b03726f00ac65b6def843d2c464 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-76339 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-81016)Record last updated .