rxrpc: Fix a race between socket set up and I/O thread creation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 56e415202b8a17de6496f4023e545fcb66f118ec, Kernel bc212465326e8587325f520a052346f0b57360e6, Kernel c64f5fc95e9612fdf75587c8e21e494e614c18e2 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.2, >=a275da62e8c111b897b9cb73eb91df2f4e475ca5 <56e415202b8a17de6496f4023e545fcb66f118ec, >=a275da62e8c111b897b9cb73eb91df2f4e475ca5 <bc212465326e8587325f520a052346f0b57360e6, >=a275da62e8c111b897b9cb73eb91df2f4e475ca5 <c64f5fc95e9612fdf75587c8e21e494e614c18e2, >=a275da62e8c111b897b9cb73eb91df2f4e475ca5 <cdf4bbbdb956d7426f687f38757ebca2a2759a0f | 56e415202b8a17de6496f4023e545fcb66f118ec, bc212465326e8587325f520a052346f0b57360e6, c64f5fc95e9612fdf75587c8e21e494e614c18e2, cdf4bbbdb956d7426f687f38757ebca2a2759a0f |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket