<?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-10-01T20:48:32.163491+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-2026-68334</id>
    <title>CVE-2026-68334 — rxrpc: fix io_thread race in rxrpc_wake_up_io_thread()</title>
    <updated>2026-10-01T20:48:32.165630+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 io_thread race in rxrpc_wake_up_io_thread()</p>
<p>rxrpc_wake_up_io_thread() checks local-&gt;io_thread before waking it, but
then reloads the pointer for wake_up_process().</p>
<p>local-&gt;io_thread is cleared with WRITE_ONCE() when the I/O thread exits, so
the second load can see NULL even if the first load did not.</p>
<p>Take a READ_ONCE() snapshot and use it for both the NULL check and the
wake_up_process() call, as rxrpc_encap_rcv() already does.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68334"/>
  </entry>
</feed>
