rxrpc: fix io_thread race in rxrpc_wake_up_io_thread()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.427.1.67.2In the Linux kernel, the following vulnerability has been resolved:
rxrpc: fix io_thread race in rxrpc_wake_up_io_thread()
rxrpc_wake_up_io_thread() checks local->io_thread before waking it, but then reloads the pointer for wake_up_process().
local->io_thread is cleared with WRITE_ONCE() when the I/O thread exits, so the second load can see NULL even if the first load did not.
Take a READ_ONCE() snapshot and use it for both the NULL check and the wake_up_process() call, as rxrpc_encap_rcv() already does.
From the CVE record · Linux
The Linux kernel's rxrpc_wake_up_io_thread() can read the I/O thread pointer twice, allowing the second read to see NULL after the thread exits. The input does not describe an attacker action, resulting impact, or conditions for exploitation.
Engineers running Linux kernels with rxrpc should check their versions; affected versions are not specified.