<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-25T13:08:16.499693+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-99032</id>
    <title>fkie_cve-2026-99032</title>
    <updated>2026-10-25T13:08:16.501996+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net/smc: protect clcsock lifetime in smc_getname</p>
<p>smc_getname() dereferences smc-&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).</p>
<p>A getsockname() caller can load smc-&gt;clcsock, then the termination worker
can clear the pointer and call sock_release() before the caller accesses
clcsock-&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's file reference keeps the SMC socket alive but does not
prevent asynchronous release of its CLC socket.</p>
<p>KASAN reported the following with test-only timing instrumentation:</p>
<p>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</p>
<p>Allocated by task 95:
   sock_alloc_inode+0x1e/0x280
   sock_alloc+0x3d/0x240
   __sock_create+0x7e/0x430
   smc_create+0x121/0x240</p>
<p>Freed by task 0:
   kmem_cache_free+0xcc/0x340
   rcu_core+0x50a/0x1850</p>
<p>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</p>
<p>Hold clcsock_release_lock across the pointer check and th…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99032"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-7g97-v76m-w626</id>
    <title>GHSA-7g97-v76m-w626</title>
    <updated>2026-10-25T13:08:16.502113+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net/smc: protect clcsock lifetime in smc_getname</p>
<p>smc_getname() dereferences smc-&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).</p>
<p>A getsockname() caller can load smc-&gt;clcsock, then the termination worker
can clear the pointer and call sock_release() before the caller accesses
clcsock-&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's file reference keeps the SMC socket alive but does not
prevent asynchronous release of its CLC socket.</p>
<p>KASAN reported the following with test-only timing instrumentation:</p>
<p>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</p>
<p>Allocated by task 95:
   sock_alloc_inode+0x1e/0x280
   sock_alloc+0x3d/0x240
   __sock_create+0x7e/0x430
   smc_create+0x121/0x240</p>
<p>Freed by task 0:
   kmem_cache_free+0xcc/0x340
   rcu_core+0x50a/0x1850</p>
<p>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</p>
<p>Hold clcsock_release_lock across the pointer check and th…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-7g97-v76m-w626"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-99032</id>
    <title>msrc_CVE-2026-99032 — net/smc: protect clcsock lifetime in smc_getname</title>
    <updated>2026-10-25T13:08:16.502177+00:00</updated>
    <content>msrc_CVE-2026-99032</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-99032"/>
  </entry>
</feed>
