CVE-2025-21803

See a problem?
Please try reporting it to the source first.
Source
https://nvd.nist.gov/vuln/detail/CVE-2025-21803
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-21803.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2025-21803
Downstream
Published
2025-02-27T20:16:02Z
Modified
2025-07-01T16:23:34.884340Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved:

LoongArch: Fix warnings during S3 suspend

The enablegpewakeup() function calls acpienableallwakeupgpes(), and the later one may call the preemptschedulecommon() function, resulting in a thread switch and causing the CPU to be in an interrupt enabled state after the enablegpewakeup() function returns, leading to the warnings as follow.

[ C0] WARNING: ... at kernel/time/timekeeping.c:845 ktimeget+0xbc/0xc8 [ C0] ... [ C0] Call Trace: [ C0] [<90000000002243b4>] showstack+0x64/0x188 [ C0] [<900000000164673c>] dumpstacklvl+0x60/0x88 [ C0] [<90000000002687e4>] _warn+0x8c/0x148 [ C0] [<90000000015e9978>] reportbug+0x1c0/0x2b0 [ C0] [<90000000016478e4>] dobp+0x204/0x3b8 [ C0] [<90000000025b1924>] exceptionhandlers+0x1924/0x10000 [ C0] [<9000000000343bbc>] ktimeget+0xbc/0xc8 [ C0] [<9000000000354c08>] tickschedtimer+0x30/0xb0 [ C0] [<90000000003408e0>] _hrtimerrunqueues+0x160/0x378 [ C0] [<9000000000341f14>] hrtimerinterrupt+0x144/0x388 [ C0] [<9000000000228348>] constanttimerinterrupt+0x38/0x48 [ C0] [<90000000002feba4>] _handleirqeventpercpu+0x64/0x1e8 [ C0] [<90000000002fed48>] handleirqeventpercpu+0x20/0x80 [ C0] [<9000000000306b9c>] handlepercpuirq+0x5c/0x98 [ C0] [<90000000002fd4a0>] generichandledomainirq+0x30/0x48 [ C0] [<9000000000d0c7b0>] handlecpuirq+0x70/0xa8 [ C0] [<9000000001646b30>] handleloongarchirq+0x30/0x48 [ C0] [<9000000001646bc8>] dovint+0x80/0xe0 [ C0] [<90000000002aea1c>] finishtaskswitch.isra.0+0x8c/0x2a8 [ C0] [<900000000164e34c>] _schedule+0x314/0xa48 [ C0] [<900000000164ead8>] schedule+0x58/0xf0 [ C0] [<9000000000294a2c>] workerthread+0x224/0x498 [ C0] [<900000000029d2f0>] kthread+0xf8/0x108 [ C0] [<9000000000221f28>] retfromkernel_thread+0xc/0xa4 [ C0] [ C0] ---[ end trace 0000000000000000 ]---

The root cause is acpienableallwakeupgpes() uses a mutex to protect acpihwenableallwakeupgpes(), and acpiutacquiremutex() may cause a thread switch. Since there is no longer concurrent execution during loongarchacpisuspend(), we can call acpihwenableallwakeupgpes() directly in enablegpe_wakeup().

The solution is similar to commit 22db06337f590d01 ("ACPI: sleep: Avoid breaking S3 wakeup due to might_sleep()").

References

Affected packages

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.12.13-1

Affected versions

6.*

6.1.27-1
6.1.37-1
6.1.38-1
6.1.38-2~bpo11+1
6.1.38-2
6.1.38-3
6.1.38-4~bpo11+1
6.1.38-4
6.1.52-1
6.1.55-1~bpo11+1
6.1.55-1
6.1.64-1
6.1.66-1
6.1.67-1
6.1.69-1~bpo11+1
6.1.69-1
6.1.76-1~bpo11+1
6.1.76-1
6.1.82-1
6.1.85-1
6.1.90-1~bpo11+1
6.1.90-1
6.1.94-1~bpo11+1
6.1.94-1
6.1.98-1
6.1.99-1
6.1.106-1
6.1.106-2
6.1.106-3
6.1.112-1
6.1.115-1
6.1.119-1
6.1.123-1
6.1.124-1
6.1.128-1
6.1.129-1
6.1.133-1
6.1.135-1
6.1.137-1
6.1.139-1
6.1.140-1
6.3.1-1~exp1
6.3.2-1~exp1
6.3.4-1~exp1
6.3.5-1~exp1
6.3.7-1~bpo12+1
6.3.7-1
6.3.11-1
6.4~rc6-1~exp1
6.4~rc7-1~exp1
6.4.1-1~exp1
6.4.4-1~bpo12+1
6.4.4-1
6.4.4-2
6.4.4-3~bpo12+1
6.4.4-3
6.4.11-1
6.4.13-1
6.5~rc4-1~exp1
6.5~rc6-1~exp1
6.5~rc7-1~exp1
6.5.1-1~exp1
6.5.3-1~bpo12+1
6.5.3-1
6.5.6-1
6.5.8-1
6.5.10-1~bpo12+1
6.5.10-1
6.5.13-1
6.6.3-1~exp1
6.6.4-1~exp1
6.6.7-1~exp1
6.6.8-1
6.6.9-1
6.6.11-1
6.6.13-1~bpo12+1
6.6.13-1
6.6.15-1
6.6.15-2
6.7-1~exp1
6.7.1-1~exp1
6.7.4-1~exp1
6.7.7-1
6.7.9-1
6.7.9-2
6.7.12-1~bpo12+1
6.7.12-1
6.8.9-1
6.8.11-1
6.8.12-1~bpo12+1
6.8.12-1
6.9.2-1~exp1
6.9.7-1~bpo12+1
6.9.7-1
6.9.8-1
6.9.9-1
6.9.10-1~bpo12+1
6.9.10-1
6.9.11-1
6.9.12-1
6.10-1~exp1
6.10.1-1~exp1
6.10.3-1
6.10.4-1
6.10.6-1~bpo12+1
6.10.6-1
6.10.7-1
6.10.9-1
6.10.11-1~bpo12+1
6.10.11-1
6.10.12-1
6.11~rc4-1~exp1
6.11~rc5-1~exp1
6.11-1~exp1
6.11.2-1
6.11.4-1
6.11.5-1~bpo12+1
6.11.5-1
6.11.6-1
6.11.7-1
6.11.9-1
6.11.10-1~bpo12+1
6.11.10-1
6.12~rc6-1~exp1
6.12.3-1
6.12.5-1
6.12.6-1
6.12.8-1
6.12.9-1~bpo12+1
6.12.9-1
6.12.9-1+alpha
6.12.10-1
6.12.11-1
6.12.11-1+alpha
6.12.11-1+alpha.1
6.12.12-1~bpo12+1
6.12.12-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}