<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 19:46:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64439 — crypto: krb5 - filter out async aead implementations at alloc</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64439</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: krb5 - filter out async aead implementations at alloc&lt;/p&gt;
&lt;p&gt;krb5_aead_encrypt(), krb5_aead_decrypt() in rfc3961_simplified.c and
rfc8009_encrypt(), rfc8009_decrypt() in rfc8009_aes2.c set a NULL
completion callback and treat any negative return from
crypto_aead_{encrypt,decrypt}() as terminal, falling through to
kfree_sensitive(buffer).  When the encrypt_name resolves to an
async AEAD instance the request returns -EINPROGRESS, the buffer
is freed while the backend&amp;#39;s worker still holds a pointer, and the
worker dereferences the freed slab on completion.&lt;/p&gt;
&lt;p&gt;KASAN report under UML+SLUB with a synthetic async aead backend
bound to krb5-&amp;gt;encrypt_name:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in t5_stub_complete+0x7d/0xc7&lt;/p&gt;
&lt;p&gt;The helpers were written synchronously, so filter the async
instances out at allocation time instead of plumbing
crypto_wait_req() through every call site.&lt;/p&gt;
&lt;p&gt;Reachable via net/rxrpc/rxgk.c, fs/afs/cm_security.c and
net/ceph/crypto.c on systems with an async AEAD provider bound to
the krb5 enctype name.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: krb5 - filter out async aead implementations at alloc&lt;/p&gt;
&lt;p&gt;krb5_aead_encrypt(), krb5_aead_decrypt() in rfc3961_simplified.c and
rfc8009_encrypt(), rfc8009_decrypt() in rfc8009_aes2.c set a NULL
completion callback and treat any negative return from
crypto_aead_{encrypt,decrypt}() as terminal, falling through to
kfree_sensitive(buffer).  When the encrypt_name resolves to an
async AEAD instance the request returns -EINPROGRESS, the buffer
is freed while the backend&amp;#39;s worker still holds a pointer, and the
worker dereferences the freed slab on completion.&lt;/p&gt;
&lt;p&gt;KASAN report under UML+SLUB with a synthetic async aead backend
bound to krb5-&amp;gt;encrypt_name:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in t5_stub_complete+0x7d/0xc7&lt;/p&gt;
&lt;p&gt;The helpers were written synchronously, so filter the async
instances out at allocation time instead of plumbing
crypto_wait_req() through every call site.&lt;/p&gt;
&lt;p&gt;Reachable via net/rxrpc/rxgk.c, fs/afs/cm_security.c and
net/ceph/crypto.c on systems with an async AEAD provider bound to
the krb5 enctype name.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64439</guid>
    </item>
  </channel>
</rss>
