<?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 07:34:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63805 — crypto: nx - fix nx_crypto_ctx_exit argument</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-63805</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: nx - fix nx_crypto_ctx_exit argument&lt;/p&gt;
&lt;p&gt;nx_crypto_ctx_shash_exit calls nx_crypto_ctx_exit with crypto_shash_ctx(...)
but crypto_shash_ctx gives a nx_crypto_ctx *, not a crypto_tfm *.&lt;/p&gt;
&lt;p&gt;Fix the type in nx_crypto_ctx_exit and drop the bogus crypto_tfm_ctx
call.&lt;/p&gt;
&lt;p&gt;This fixes the following oops:&lt;/p&gt;
&lt;p&gt;BUG: Unable to handle kernel data access at 0xc0403effffffffc8
  Faulting instruction address: 0xc000000000396cb4
  Oops: Kernel access of bad area, sig: 11 [#15]
  Call Trace:
   nx_crypto_ctx_shash_exit+0x24/0x60
   crypto_shash_exit_tfm+0x28/0x40
   crypto_destroy_tfm+0x98/0x140
   crypto_exit_ahash_using_shash+0x20/0x40
   crypto_destroy_tfm+0x98/0x140
   hash_release+0x1c/0x30
   alg_sock_destruct+0x38/0x60
   __sk_destruct+0x48/0x2b0
   af_alg_release+0x58/0xb0
   __sock_release+0x68/0x150
   sock_close+0x20/0x40
   __fput+0x110/0x3a0
   sys_close+0x48/0xa0
   system_call_exception+0x140/0x2d0
   system_call_common+0xf4/0x258&lt;/p&gt;
&lt;p&gt;.. which came from hardlink(1) opportunistically using AF_ALG.&lt;/p&gt;
&lt;p&gt;The same problem exists with nx_crypto_ctx_skcipher_exit getting a context
it wasn&amp;#39;t expecting, but apparently nobody hit that for years.&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: nx - fix nx_crypto_ctx_exit argument&lt;/p&gt;
&lt;p&gt;nx_crypto_ctx_shash_exit calls nx_crypto_ctx_exit with crypto_shash_ctx(...)
but crypto_shash_ctx gives a nx_crypto_ctx *, not a crypto_tfm *.&lt;/p&gt;
&lt;p&gt;Fix the type in nx_crypto_ctx_exit and drop the bogus crypto_tfm_ctx
call.&lt;/p&gt;
&lt;p&gt;This fixes the following oops:&lt;/p&gt;
&lt;p&gt;BUG: Unable to handle kernel data access at 0xc0403effffffffc8
  Faulting instruction address: 0xc000000000396cb4
  Oops: Kernel access of bad area, sig: 11 [#15]
  Call Trace:
   nx_crypto_ctx_shash_exit+0x24/0x60
   crypto_shash_exit_tfm+0x28/0x40
   crypto_destroy_tfm+0x98/0x140
   crypto_exit_ahash_using_shash+0x20/0x40
   crypto_destroy_tfm+0x98/0x140
   hash_release+0x1c/0x30
   alg_sock_destruct+0x38/0x60
   __sk_destruct+0x48/0x2b0
   af_alg_release+0x58/0xb0
   __sock_release+0x68/0x150
   sock_close+0x20/0x40
   __fput+0x110/0x3a0
   sys_close+0x48/0xa0
   system_call_exception+0x140/0x2d0
   system_call_common+0xf4/0x258&lt;/p&gt;
&lt;p&gt;.. which came from hardlink(1) opportunistically using AF_ALG.&lt;/p&gt;
&lt;p&gt;The same problem exists with nx_crypto_ctx_skcipher_exit getting a context
it wasn&amp;#39;t expecting, but apparently nobody hit that for years.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-63805</guid>
    </item>
  </channel>
</rss>
