CVE-2025-21645
Vulnerability from cvelistv5
Published
2025-01-19 10:18
Modified
2025-01-20 06:30
Severity ?
EPSS score ?
Summary
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.]
References
Impacted products
{ "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "drivers/platform/x86/amd/pmc/pmc.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "5cc621085e2b7a9b1905a98f8e5a86bb4aea2016", "status": "affected", "version": "8e60615e8932167057b363c11a7835da7f007106", "versionType": "git" }, { "lessThan": "b25778c87a6bce40c31e92364f08aa6240309e25", "status": "affected", "version": "8e60615e8932167057b363c11a7835da7f007106", "versionType": "git" }, { "lessThan": "dd410d784402c5775f66faf8b624e85e41c38aaf", "status": "affected", "version": "8e60615e8932167057b363c11a7835da7f007106", "versionType": "git" } ] }, { "defaultStatus": "affected", "product": "Linux", "programFiles": [ "drivers/platform/x86/amd/pmc/pmc.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "status": "affected", "version": "6.2" }, { "lessThan": "6.2", "status": "unaffected", "version": "0", "versionType": "semver" }, { "lessThanOrEqual": "6.6.*", "status": "unaffected", "version": "6.6.72", "versionType": "semver" }, { "lessThanOrEqual": "6.12.*", "status": "unaffected", "version": "6.12.10", "versionType": "semver" }, { "lessThanOrEqual": "*", "status": "unaffected", "version": "6.13", "versionType": "original_commit_for_fix" } ] } ], "descriptions": [ { "lang": "en", "value": "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.]" } ], "providerMetadata": { "dateUpdated": "2025-01-20T06:30:04.519Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/5cc621085e2b7a9b1905a98f8e5a86bb4aea2016" }, { "url": "https://git.kernel.org/stable/c/b25778c87a6bce40c31e92364f08aa6240309e25" }, { "url": "https://git.kernel.org/stable/c/dd410d784402c5775f66faf8b624e85e41c38aaf" } ], "title": "platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it", "x_generator": { "engine": "bippy-5f407fcff5a0" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2025-21645", "datePublished": "2025-01-19T10:18:01.556Z", "dateReserved": "2024-12-29T08:45:45.728Z", "dateUpdated": "2025-01-20T06:30:04.519Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "vulnerability-lookup:meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2025-21645\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-19T11:15:10.090\",\"lastModified\":\"2025-01-19T11:15:10.090\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.]\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/5cc621085e2b7a9b1905a98f8e5a86bb4aea2016\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b25778c87a6bce40c31e92364f08aa6240309e25\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/dd410d784402c5775f66faf8b624e85e41c38aaf\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}" } }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.