<?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:53:21.126143+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-31639</id>
    <title>CVE-2026-31639 — rxrpc: Fix key reference count leak from call-&gt;key</title>
    <updated>2026-09-29T11:53:21.555293+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 key reference count leak from call-&gt;key</p>
<p>When creating a client call in rxrpc_alloc_client_call(), the code obtains
a reference to the key.  This is never cleaned up and gets leaked when the
call is destroyed.</p>
<p>Fix this by freeing call-&gt;key in rxrpc_destroy_call().</p>
<p>Before the patch, it shows the key reference counter elevated:</p>
<p>$ cat /proc/keys | grep afs@54321
1bffe9cd I--Q--i 8053480 4169w 3b010000  1000  1000 rxrpc     afs@54321: ka
$</p>
<p>After the patch, the invalidated key is removed when the code exits:</p>
<p>$ cat /proc/keys | grep afs@54321
$</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31639"/>
  </entry>
</feed>
