rxrpc: Fix missing locking causing hanging calls
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.6.616.11.86.12In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix missing locking causing hanging calls
If a call gets aborted (e.g. because kafs saw a signal) between it being queued for connection and the I/O thread picking up the call, the abort will be prioritised over the connection and it will be removed from local->new_client_calls by rxrpc_disconnect_client_call() without a lock being held. This may cause other calls on the list to disappear if a race occurs.
Fix this by taking the client_call_lock when removing a call from whatever list its ->wait_link happens to be on.
From the CVE record · Linux
A missing lock in the Linux kernel's rxrpc code can cause calls to hang. If a call is aborted after it is queued for a connection but before the I/O thread picks it up, a race can cause other queued calls to disappear. The input does not specify attacker access requirements or user interaction.
Engineers running the Linux kernel with rxrpc should check their deployments; affected versions are not specified.