{"uuid": "d425a727-522a-46f8-92b3-93339e47ab17", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21645", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2321", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21645\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it\n\nWakeup for IRQ1 should be disabled only in cases where i8042 had\nactually enabled it, otherwise \"wake_depth\" for this IRQ will try to\ndrop below zero and there will be an unpleasant WARN() logged:\n\nkernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug\nkernel: ------------[ cut here ]------------\nkernel: Unbalanced IRQ 1 wake disable\nkernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0\n\nThe PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops\nwhich sets amd_pmc_suspend_handler() to the .suspend, .freeze, and\n.poweroff handlers. i8042_pm_suspend(), however, is only set as\nthe .suspend handler.\n\nFix the issue by call PMC suspend handler only from the same set of\ndev_pm_ops handlers as i8042_pm_suspend(), which currently means just\nthe .suspend handler.\n\nTo reproduce this issue try hibernating (S4) the machine after a fresh boot\nwithout putting it into s2idle first.\n\n[ij: edited the commit message.]\n\ud83d\udccf Published: 2025-01-19T10:18:01.556Z\n\ud83d\udccf Modified: 2025-01-19T10:18:01.556Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/5cc621085e2b7a9b1905a98f8e5a86bb4aea2016\n2. https://git.kernel.org/stable/c/b25778c87a6bce40c31e92364f08aa6240309e25\n3. https://git.kernel.org/stable/c/dd410d784402c5775f66faf8b624e85e41c38aaf", "creation_timestamp": "2025-01-19T10:58:26.000000Z"}