locking/spinlock/debug: Fix data-race in do_raw_write_lock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1a365e822372ba24c9da0822bc583894f6f3d821 · < 16b3590c0e1e615757dade098c8fbc0d4f040c76| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
locking/spinlock/debug: Fix data-race in do_raw_write_lock
KCSAN reports:
BUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock
write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1: do_raw_write_lock+0x120/0x204 _raw_write_lock_irq do_exit call_usermodehelper_exec_async ret_from_fork
read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0: do_raw_write_lock+0x88/0x204 _raw_write_lock_irq do_exit call_usermodehelper_exec_async ret_from_fork
value changed: 0xffffffff -> 0x00000001
Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111
From the CVE record · Linux
A data race in the Linux kernel’s do_raw_write_lock function can cause concurrent reads and writes of the same lock-debugging value. The report does not specify an attacker action, access requirements, or user interaction.
Engineers running the Linux kernel should check their deployments; the race was reported on kernel 6.1.111, but the affected version range is not specified.