<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 13:12:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-81016 — platform/x86/amd/pmc: Propagate SMU errors and validate S2D address</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-81016</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;platform/x86/amd/pmc: Propagate SMU errors and validate S2D address&lt;/p&gt;
&lt;p&gt;amd_stb_s2d_init() discards the return value of several S2D SMU commands.
When the SMU refuses a command (e.g. &amp;#34;SMU cmd failed. err: 0xff&amp;#34;) the
failure is only noticed indirectly - if at all - and reported as -EIO,
masking the real error.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;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:...&lt;/p&gt;
&lt;p&gt;Check the return value of each SMU command and propagate it, and reject a
zero physical address before calling devm_ioremap().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;platform/x86/amd/pmc: Propagate SMU errors and validate S2D address&lt;/p&gt;
&lt;p&gt;amd_stb_s2d_init() discards the return value of several S2D SMU commands.
When the SMU refuses a command (e.g. &amp;#34;SMU cmd failed. err: 0xff&amp;#34;) the
failure is only noticed indirectly - if at all - and reported as -EIO,
masking the real error.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;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:...&lt;/p&gt;
&lt;p&gt;Check the return value of each SMU command and propagate it, and reject a
zero physical address before calling devm_ioremap().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-81016</guid>
    </item>
  </channel>
</rss>
