<?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-28T18:17:14.274498+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-31640</id>
    <title>CVE-2026-31640 — rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial</title>
    <updated>2026-09-28T18:17:14.381745+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 use of wrong skb when comparing queued RESP challenge serial</p>
<p>In rxrpc_post_response(), the code should be comparing the challenge serial
number from the cached response before deciding to switch to a newer
response, but looks at the newer packet private data instead, rendering the
comparison always false.</p>
<p>Fix this by switching to look at the older packet.</p>
<p>Fix further[1] to substitute the new packet in place of the old one if
newer and also to release whichever we don't use.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31640"/>
  </entry>
</feed>
