CVE-2025-68336: locking/spinlock/debug: Fix data-race in do_raw_write_lock
In the Linux kernel, the following vulnerability has been resolved:
locking/spinlock/debug: Fix data-race in dorawwritelock
KCSAN reports:
BUG: KCSAN: data-race in dorawwritelock / dorawwritelock
write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1: dorawwritelock+0x120/0x204 rawwritelockirq doexit callusermodehelperexecasync retfromfork
read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0: dorawwritelock+0x88/0x204 rawwritelockirq doexit callusermodehelperexecasync retfromfork
value changed: 0xffffffff -> 0x00000001
Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111
Commit 1a365e822372 ("locking/spinlock/debug: Fix various data races") has adressed most of these races, but seems to be not consistent/not complete.
From dorawwritelock() only debugwritelockafter() part has been converted to WRITEONCE(), but not debugwritelockbefore() part. Do it now.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch 1a365e822372
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68336?
CVE-2025-68336 has been classified with a severity level that indicates a potential data-race condition in the Linux kernel.
How do I fix CVE-2025-68336?
To fix CVE-2025-68336, ensure that you update to the latest version of the Linux kernel where the vulnerability has been addressed.
What impact does CVE-2025-68336 have on system performance?
CVE-2025-68336 can lead to unpredictable behavior in the Linux kernel, which may negatively affect system performance and stability.
Is CVE-2025-68336 a remote exploit?
CVE-2025-68336 is related to a data race condition locally within the kernel and is not considered a remote exploit.
What versions of the Linux kernel are affected by CVE-2025-68336?
CVE-2025-68336 affects various versions of the Linux kernel prior to the fix, but specific affected versions should be checked against the provided update.