<?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://db.gcve.eu</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>Sun, 25 Oct 2026 22:49:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99032 — net/smc: protect clcsock lifetime in smc_getname</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99032</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;net/smc: protect clcsock lifetime in smc_getname&lt;/p&gt;
&lt;p&gt;smc_getname() dereferences smc-&amp;gt;clcsock without holding
clcsock_release_lock. Link-group termination can release the CLC socket
through smc_close_active_abort() while the SMC socket is still open,
for example after shutdown(SHUT_WR).&lt;/p&gt;
&lt;p&gt;A getsockname() caller can load smc-&amp;gt;clcsock, then the termination worker
can clear the pointer and call sock_release() before the caller accesses
clcsock-&amp;gt;ops or invokes getname(). This causes a use-after-free; if the
worker clears the pointer before the load, it causes a NULL dereference.
The syscall&amp;#39;s file reference keeps the SMC socket alive but does not
prevent asynchronous release of its CLC socket.&lt;/p&gt;
&lt;p&gt;KASAN reported the following with test-only timing instrumentation:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0
  Read of size 8 at addr ffff888109abb4e0 by task poc/103
  Call Trace:
   smc_getname+0x19e/0x1b0
   do_getsockname+0xe5/0x170
   __sys_getsockname+0x8c/0x100&lt;/p&gt;
&lt;p&gt;Allocated by task 95:
   sock_alloc_inode+0x1e/0x280
   sock_alloc+0x3d/0x240
   __sock_create+0x7e/0x430
   smc_create+0x121/0x240&lt;/p&gt;
&lt;p&gt;Freed by task 0:
   kmem_cache_free+0xcc/0x340
   rcu_core+0x50a/0x1850&lt;/p&gt;
&lt;p&gt;Last potentially related work creation:
   evict+0x446/0x6c0
   smc_clcsock_release+0xa8/0xd0
   smc_close_active_abort+0x26a/0x3a0
   __smc_lgr_terminate.part.0+0x137/0x2e0&lt;/p&gt;
&lt;p&gt;Hold clcsock_release_lock across the pointer check and th…&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;net/smc: protect clcsock lifetime in smc_getname&lt;/p&gt;
&lt;p&gt;smc_getname() dereferences smc-&amp;gt;clcsock without holding
clcsock_release_lock. Link-group termination can release the CLC socket
through smc_close_active_abort() while the SMC socket is still open,
for example after shutdown(SHUT_WR).&lt;/p&gt;
&lt;p&gt;A getsockname() caller can load smc-&amp;gt;clcsock, then the termination worker
can clear the pointer and call sock_release() before the caller accesses
clcsock-&amp;gt;ops or invokes getname(). This causes a use-after-free; if the
worker clears the pointer before the load, it causes a NULL dereference.
The syscall&amp;#39;s file reference keeps the SMC socket alive but does not
prevent asynchronous release of its CLC socket.&lt;/p&gt;
&lt;p&gt;KASAN reported the following with test-only timing instrumentation:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0
  Read of size 8 at addr ffff888109abb4e0 by task poc/103
  Call Trace:
   smc_getname+0x19e/0x1b0
   do_getsockname+0xe5/0x170
   __sys_getsockname+0x8c/0x100&lt;/p&gt;
&lt;p&gt;Allocated by task 95:
   sock_alloc_inode+0x1e/0x280
   sock_alloc+0x3d/0x240
   __sock_create+0x7e/0x430
   smc_create+0x121/0x240&lt;/p&gt;
&lt;p&gt;Freed by task 0:
   kmem_cache_free+0xcc/0x340
   rcu_core+0x50a/0x1850&lt;/p&gt;
&lt;p&gt;Last potentially related work creation:
   evict+0x446/0x6c0
   smc_clcsock_release+0xa8/0xd0
   smc_close_active_abort+0x26a/0x3a0
   __smc_lgr_terminate.part.0+0x137/0x2e0&lt;/p&gt;
&lt;p&gt;Hold clcsock_release_lock across the pointer check and th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99032</guid>
    </item>
  </channel>
</rss>
