CVE-2025-21645

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it<br /> <br /> Wakeup for IRQ1 should be disabled only in cases where i8042 had<br /> actually enabled it, otherwise "wake_depth" for this IRQ will try to<br /> drop below zero and there will be an unpleasant WARN() logged:<br /> <br /> kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug<br /> kernel: ------------[ cut here ]------------<br /> kernel: Unbalanced IRQ 1 wake disable<br /> kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0<br /> <br /> The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops<br /> which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and<br /> .poweroff handlers. i8042_pm_suspend(), however, is only set as<br /> the .suspend handler.<br /> <br /> Fix the issue by call PMC suspend handler only from the same set of<br /> dev_pm_ops handlers as i8042_pm_suspend(), which currently means just<br /> the .suspend handler.<br /> <br /> To reproduce this issue try hibernating (S4) the machine after a fresh boot<br /> without putting it into s2idle first.<br /> <br /> [ij: edited the commit message.]