platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it

Summary

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: 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 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. 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. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]

Timeline

1. Jan 19, 2025, 10:18 AM UTCCVE published
2. Oct 15, 2026, 1:02 AM UTCRecord last updated

Affected versions

• Linux Linux

  From 72e5a83b7c8401856cc3732150af24e43726717a · fixed in ab47d72b736e78d3c2370b26e0bfc46eb0918391; From 8e60615e8932167057b363c11a7835da7f007106 · fixed in 5cc621085e2b7a9b1905a98f8e5a86bb4aea2016; From 8e60615e8932167057b363c11a7835da7f007106 · fixed in b25778c87a6bce40c31e92364f08aa6240309e25; From 8e60615e8932167057b363c11a7835da7f007106 · fixed in dd410d784402c5775f66faf8b624e85e41c38aaf; From 6.1.11 · fixed in 6.1.140; From 5.15.95 · fixed in 5.16

• Linux Linux

  6.2

• KernelLinux

  fixed in 6.1.140; From 6.2.0 · fixed in 6.6.72; fixed in 6.12.10

References 4