<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 21:10:51 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74493</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74493</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74493</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1090 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090</link>
      <description>certfr-2026-avi-1090</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090</guid>
    </item>
    <item>
      <title>EUVD-2026-356398</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-356398</link>
      <description>EUVD-2026-356398</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-356398</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74493</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74493</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/smc: fix socket use-after-free during link group termination&lt;/p&gt;
&lt;p&gt;__smc_lgr_terminate() drops conns_lock after finding a connection in
lgr-&amp;gt;conns_all, but before taking a reference on its socket. The connection
is embedded in the socket, and its registration reference protects it only
while the connection remains in the tree.&lt;/p&gt;
&lt;p&gt;A concurrent close can unregister the connection and drop that reference,
freeing the socket before the termination worker reaches sock_hold().&lt;/p&gt;
&lt;p&gt;The race is reachable when close overlaps link group termination.
Local stress testing reproduced the use-after-free and KASAN reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc]
  Write of size 4 by task kworker/3:3
  Workqueue: events smc_lgr_terminate_work [smc]
  __smc_lgr_terminate.part.0 [smc]&lt;/p&gt;
&lt;p&gt;The socket was allocated by smc_create(), freed through
slab_free_after_rcu_debug(), and was followed by:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
  __smc_lgr_terminate.part.0 [smc]&lt;/p&gt;
&lt;p&gt;Take the socket reference while conns_lock still protects the tree entry.
The unregister path then cannot drop the last reference until termination
has finished using the socket.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/smc: fix socket use-after-free during link group termination&lt;/p&gt;
&lt;p&gt;__smc_lgr_terminate() drops conns_lock after finding a connection in
lgr-&amp;gt;conns_all, but before taking a reference on its socket. The connection
is embedded in the socket, and its registration reference protects it only
while the connection remains in the tree.&lt;/p&gt;
&lt;p&gt;A concurrent close can unregister the connection and drop that reference,
freeing the socket before the termination worker reaches sock_hold().&lt;/p&gt;
&lt;p&gt;The race is reachable when close overlaps link group termination.
Local stress testing reproduced the use-after-free and KASAN reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc]
  Write of size 4 by task kworker/3:3
  Workqueue: events smc_lgr_terminate_work [smc]
  __smc_lgr_terminate.part.0 [smc]&lt;/p&gt;
&lt;p&gt;The socket was allocated by smc_create(), freed through
slab_free_after_rcu_debug(), and was followed by:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
  __smc_lgr_terminate.part.0 [smc]&lt;/p&gt;
&lt;p&gt;Take the socket reference while conns_lock still protects the tree entry.
The unregister path then cannot drop the last reference until termination
has finished using the socket.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74493</guid>
    </item>
    <item>
      <title>GHSA-xhjj-46q7-2hx6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xhjj-46q7-2hx6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/smc: fix socket use-after-free during link group termination&lt;/p&gt;
&lt;p&gt;__smc_lgr_terminate() drops conns_lock after finding a connection in
lgr-&amp;gt;conns_all, but before taking a reference on its socket. The connection
is embedded in the socket, and its registration reference protects it only
while the connection remains in the tree.&lt;/p&gt;
&lt;p&gt;A concurrent close can unregister the connection and drop that reference,
freeing the socket before the termination worker reaches sock_hold().&lt;/p&gt;
&lt;p&gt;The race is reachable when close overlaps link group termination.
Local stress testing reproduced the use-after-free and KASAN reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc]
  Write of size 4 by task kworker/3:3
  Workqueue: events smc_lgr_terminate_work [smc]
  __smc_lgr_terminate.part.0 [smc]&lt;/p&gt;
&lt;p&gt;The socket was allocated by smc_create(), freed through
slab_free_after_rcu_debug(), and was followed by:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
  __smc_lgr_terminate.part.0 [smc]&lt;/p&gt;
&lt;p&gt;Take the socket reference while conns_lock still protects the tree entry.
The unregister path then cannot drop the last reference until termination
has finished using the socket.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/smc: fix socket use-after-free during link group termination&lt;/p&gt;
&lt;p&gt;__smc_lgr_terminate() drops conns_lock after finding a connection in
lgr-&amp;gt;conns_all, but before taking a reference on its socket. The connection
is embedded in the socket, and its registration reference protects it only
while the connection remains in the tree.&lt;/p&gt;
&lt;p&gt;A concurrent close can unregister the connection and drop that reference,
freeing the socket before the termination worker reaches sock_hold().&lt;/p&gt;
&lt;p&gt;The race is reachable when close overlaps link group termination.
Local stress testing reproduced the use-after-free and KASAN reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc]
  Write of size 4 by task kworker/3:3
  Workqueue: events smc_lgr_terminate_work [smc]
  __smc_lgr_terminate.part.0 [smc]&lt;/p&gt;
&lt;p&gt;The socket was allocated by smc_create(), freed through
slab_free_after_rcu_debug(), and was followed by:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
  __smc_lgr_terminate.part.0 [smc]&lt;/p&gt;
&lt;p&gt;Take the socket reference while conns_lock still protects the tree entry.
The unregister path then cannot drop the last reference until termination
has finished using the socket.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xhjj-46q7-2hx6</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-74493 — net/smc: fix socket use-after-free during link group termination</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-74493</link>
      <description>msrc_CVE-2026-74493</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-74493</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74493</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74493</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/smc: fix socket use-after-free during link group termination __smc_lgr_terminate() drops conns_lock after finding a connection in lgr-&amp;gt;conns_all, but before taking a reference on its socket. The connection is embedded in the socket, and its registration reference protects it only while the connection remains in the tree. A concurrent close can unregister the connection and drop that reference, freeing the socket before the termination worker reaches sock_hold(). The race is reachable when close overlaps link group termination. Local stress testing reproduced the use-after-free and KASAN reported:   BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc]   Write of size 4 by task kworker/3:3   Workqueue: events smc_lgr_terminate_work [smc]   __smc_lgr_terminate.part.0 [smc] The socket was allocated by smc_create(), freed through slab_free_after_rcu_debug(), and was followed by:   refcount_t: addition on 0; use-after-free.   __smc_lgr_terminate.part.0 [smc] Take the socket reference while conns_lock still protects the tree entry. The unregister path then cannot drop the last reference until termination has finished using the socket.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/smc: fix socket use-after-free during link group termination __smc_lgr_terminate() drops conns_lock after finding a connection in lgr-&amp;gt;conns_all, but before taking a reference on its socket. The connection is embedded in the socket, and its registration reference protects it only while the connection remains in the tree. A concurrent close can unregister the connection and drop that reference, freeing the socket before the termination worker reaches sock_hold(). The race is reachable when close overlaps link group termination. Local stress testing reproduced the use-after-free and KASAN reported:   BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc]   Write of size 4 by task kworker/3:3   Workqueue: events smc_lgr_terminate_work [smc]   __smc_lgr_terminate.part.0 [smc] The socket was allocated by smc_create(), freed through slab_free_after_rcu_debug(), and was followed by:   refcount_t: addition on 0; use-after-free.   __smc_lgr_terminate.part.0 [smc] Take the socket reference while conns_lock still protects the tree entry. The unregister path then cannot drop the last reference until termination has finished using the socket.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74493</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
