{"uuid": "8edf9d23-54cb-4b07-a99d-6ffd6826e76f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21645", "type": "seen", "source": "https://t.me/cvedetector/15824", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21645 - AMD PMC Linux Kernel Wakeup Handling Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21645 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : 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.] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:07:07.000000Z"}