https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 08:23:32 +0000 https://vulnerability.circl.lu/vuln/cve-2024-49864 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rxrpc: Fix a race between socket set up and I/O thread creation</p> <p>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&#39;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.</p> <p>As a quick fix, just make rxrpc_encap_rcv() discard the packet if there&#39;s no I/O thread yet.</p> <p>A better, but more intrusive fix would perhaps be to rearrange things such that the socket creation is done by the I/O thread.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rxrpc: Fix a race between socket set up and I/O thread creation</p> <p>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&#39;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.</p> <p>As a quick fix, just make rxrpc_encap_rcv() discard the packet if there&#39;s no I/O thread yet.</p> <p>A better, but more intrusive fix would perhaps be to rearrange things such that the socket creation is done by the I/O thread.</p> https://vulnerability.circl.lu/vuln/cve-2024-49864