CVE-2025-21645 Details
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.]
A vulnerability in the Linux kernel's PMC driver related to improper management of the IRQ1 wakeup source has been addressed. The issue arose because the PMC driver disabled the IRQ1 wakeup without confirming whether it had been enabled by the i8042 controller. This oversight could cause the 'wake_depth' for IRQ1 to drop below zero, triggering a warning in the kernel logs about an unbalanced IRQ wake disable. The vulnerability was rooted in the PMC driver's power management operations, which were not aligned with the i8042's suspend handling. The problem could be reproduced by hibernating the machine after a fresh boot, without first entering a low-power state.
The vulnerability has been fixed in the Linux kernel by ensuring that the PMC driver's suspend handler is called only from the same set of device power management operations as the i8042 suspend handler.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.15.95, < 5.16 >= 6.1.11, < 6.1.140 >= 6.2.1, < 6.6.72 >= 6.7, < 6.12.10 6.2 - 6.2 rc6 6.2 rc7 6.2 rc8 6.13 rc1 6.13 rc2 6.13 rc3 6.13 rc4 6.13 rc5 6.13 rc6 |
CPE
Remediation
| |
Change History
11 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 10, 2026 | CVE Modified | siemens-SADP |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Oct 15, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | CVE |
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| Jul 14, 2026 | CVE Modified | siemens-SADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 3, 2025 | CVE Modified | CVE |
| Oct 16, 2025 | Initial Analysis | [email protected] |
| May 22, 2025 | CVE Modified | kernel.org |
| Jan 19, 2025 | New CVE Received | kernel.org |