CVE-2025-21645: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it
First published: Sun Jan 19 2025(Updated: )
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.]
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | <=6.1.129-1<=6.1.128-1 | 5.10.223-1 5.10.234-1 6.12.20-1 6.12.21-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/5cc621085e2b7a9b1905a98f8e5a86bb4aea2016
- https://git.kernel.org/stable/c/b25778c87a6bce40c31e92364f08aa6240309e25
- https://git.kernel.org/stable/c/dd410d784402c5775f66faf8b624e85e41c38aaf
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21645
- https://nvd.nist.gov/vuln/detail/CVE-2025-21645
- https://launchpad.net/bugs/cve/CVE-2025-21645
- https://security-tracker.debian.org/tracker/CVE-2025-21645
- https://ubuntu.com/security/CVE-2025-21645
- https://git.kernel.org/linus/dd410d784402c5775f66faf8b624e85e41c38aaf
Frequently Asked Questions
What is the severity of CVE-2025-21645?
The CVE-2025-21645 vulnerability has a medium severity rating as it affects the interrupt handling in the Linux kernel.
How do I fix CVE-2025-21645?
To fix CVE-2025-21645, you should update to the latest version of the Linux kernel where this vulnerability has been addressed.
What type of systems are affected by CVE-2025-21645?
CVE-2025-21645 affects systems running vulnerable versions of the Linux kernel that utilize the i8042 keyboard controller.
What is the impact of CVE-2025-21645 on system performance?
CVE-2025-21645 can potentially lead to improper wakeup handling for IRQ1, which may affect system responsiveness during sleep states.
Is CVE-2025-21645 being actively exploited in the wild?
As of now, there is no public indication that CVE-2025-21645 is being actively exploited in the wild.
- collector/nvd-api
- source/NVD
- agent/first-publish-date
- agent/type
- agent/title
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/description
- agent/source
- agent/tags
- agent/softwarecombine
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian