<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 19:11:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21645 — platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21645</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&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: Only disable IRQ1 wakeup where i8042 actually enabled it&lt;/p&gt;
&lt;p&gt;Wakeup for IRQ1 should be disabled only in cases where i8042 had
actually enabled it, otherwise &amp;#34;wake_depth&amp;#34; for this IRQ will try to
drop below zero and there will be an unpleasant WARN() logged:&lt;/p&gt;
&lt;p&gt;kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug
kernel: ------------[ cut here ]------------
kernel: Unbalanced IRQ 1 wake disable
kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0&lt;/p&gt;
&lt;p&gt;The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops
which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and
.poweroff handlers. i8042_pm_suspend(), however, is only set as
the .suspend handler.&lt;/p&gt;
&lt;p&gt;Fix the issue by call PMC suspend handler only from the same set of
dev_pm_ops handlers as i8042_pm_suspend(), which currently means just
the .suspend handler.&lt;/p&gt;
&lt;p&gt;To reproduce this issue try hibernating (S4) the machine after a fresh boot
without putting it into s2idle first.&lt;/p&gt;
&lt;p&gt;[ij: edited the commit message.]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&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: Only disable IRQ1 wakeup where i8042 actually enabled it&lt;/p&gt;
&lt;p&gt;Wakeup for IRQ1 should be disabled only in cases where i8042 had
actually enabled it, otherwise &amp;#34;wake_depth&amp;#34; for this IRQ will try to
drop below zero and there will be an unpleasant WARN() logged:&lt;/p&gt;
&lt;p&gt;kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug
kernel: ------------[ cut here ]------------
kernel: Unbalanced IRQ 1 wake disable
kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0&lt;/p&gt;
&lt;p&gt;The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops
which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and
.poweroff handlers. i8042_pm_suspend(), however, is only set as
the .suspend handler.&lt;/p&gt;
&lt;p&gt;Fix the issue by call PMC suspend handler only from the same set of
dev_pm_ops handlers as i8042_pm_suspend(), which currently means just
the .suspend handler.&lt;/p&gt;
&lt;p&gt;To reproduce this issue try hibernating (S4) the machine after a fresh boot
without putting it into s2idle first.&lt;/p&gt;
&lt;p&gt;[ij: edited the commit message.]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21645</guid>
    </item>
  </channel>
</rss>
