rxrpc: Fix a race between socket set up and I/O thread creation
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix a race between socket set up and I/O thread creation
In rxrpc_open_socket(), it sets up the socket and then sets up the I/O thread that will handle it. This is a problem, however, as there's a gap between the two phases in which a packet may come into rxrpc_encap_rcv() from the UDP packet but we oops when trying to wake the not-yet created I/O thread.
As a quick fix, just make rxrpc_encap_rcv() discard the packet if there's no I/O thread yet.
A better, but more intrusive fix would perhaps be to rearrange things such that the socket creation is done by the I/O thread.
From the CVE record · Linux
A race in Linux kernel rxrpc socket setup can let an incoming UDP packet reach the receive handler before its I/O thread exists. This can cause a kernel oops when the handler tries to wake that thread. The input does not specify authentication or user-interaction requirements.
Anyone running a Linux kernel with rxrpc should check whether their kernel includes the fix; affected versions are not specified.