<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T11:35:28.001542+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-49864</id>
    <title>CVE-2024-49864 — rxrpc: Fix a race between socket set up and I/O thread creation</title>
    <updated>2026-09-29T11:35:28.002475+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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'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'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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-49864"/>
  </entry>
</feed>
