<?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>Thu, 01 Oct 2026 15:40:48 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-90171 — CVE-2026-90171 does not affect BellSoft software</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-90171</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-90171</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90171</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-90171</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: smbdirect: release pending child sockets outside the handler lock&lt;/p&gt;
&lt;p&gt;smbdirect_socket_destroy() releases the listener&amp;#39;s pending/ready child
sockets while still holding the listener&amp;#39;s handler lock, the
&amp;amp;id_priv-&amp;gt;handler_mutex taken via rdma_lock_handler(), not
sc-&amp;gt;listen.lock, and before the listener&amp;#39;s own rdma_destroy_id().
That ordering has one real consequence and one cosmetic one.&lt;/p&gt;
&lt;p&gt;The real one: smbdirect_socket_release() drops the child&amp;#39;s last
reference, which destroys the child&amp;#39;s cm_id.  Doing that before the
listener&amp;#39;s rdma_destroy_id() lets _cma_cancel_listens(), running from
the listener&amp;#39;s _destroy_id(), walk an already freed child id_priv,
which KASAN catches as a slab-use-after-free during listener shutdown:&lt;/p&gt;
&lt;p&gt;[ 4758.909130] BUG: KASAN: slab-use-after-free in __mutex_lock+0x1469/0x1560
[ 4758.911450] Read of size 1 at addr ffff88821c381db4 by task ksmbd.control/1652
[ 4758.913262] Call Trace:
[ 4758.913267]  &amp;lt;TASK&amp;gt;
[ 4758.913299]  __mutex_lock+0x1469/0x1560
[ 4758.913408]  _cma_cancel_listens+0x312/0x3b0
[ 4758.913413]  _destroy_id+0x363/0xee0
[ 4758.913417]  smbdirect_socket_destroy_sync+0x17d5/0x2440
[ 4758.913443]  smbdirect_socket_release+0x124/0x230
[ 4758.913451]  ksmbd_rdma_stop_listening+0x9f/0x190
[ 4758.913457]  ksmbd_conn_transport_destroy+0x65/0x3c0
[ 4758.913463]  kill_server_store+0x1fb/0x2b0
[ 4758.913501]  kernfs_fop_write_iter+0x349/0x4d0
[ 4758.913507]  vfs_write+0x5e7/0xc70
[…&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;smb: smbdirect: release pending child sockets outside the handler lock&lt;/p&gt;
&lt;p&gt;smbdirect_socket_destroy() releases the listener&amp;#39;s pending/ready child
sockets while still holding the listener&amp;#39;s handler lock, the
&amp;amp;id_priv-&amp;gt;handler_mutex taken via rdma_lock_handler(), not
sc-&amp;gt;listen.lock, and before the listener&amp;#39;s own rdma_destroy_id().
That ordering has one real consequence and one cosmetic one.&lt;/p&gt;
&lt;p&gt;The real one: smbdirect_socket_release() drops the child&amp;#39;s last
reference, which destroys the child&amp;#39;s cm_id.  Doing that before the
listener&amp;#39;s rdma_destroy_id() lets _cma_cancel_listens(), running from
the listener&amp;#39;s _destroy_id(), walk an already freed child id_priv,
which KASAN catches as a slab-use-after-free during listener shutdown:&lt;/p&gt;
&lt;p&gt;[ 4758.909130] BUG: KASAN: slab-use-after-free in __mutex_lock+0x1469/0x1560
[ 4758.911450] Read of size 1 at addr ffff88821c381db4 by task ksmbd.control/1652
[ 4758.913262] Call Trace:
[ 4758.913267]  &amp;lt;TASK&amp;gt;
[ 4758.913299]  __mutex_lock+0x1469/0x1560
[ 4758.913408]  _cma_cancel_listens+0x312/0x3b0
[ 4758.913413]  _destroy_id+0x363/0xee0
[ 4758.913417]  smbdirect_socket_destroy_sync+0x17d5/0x2440
[ 4758.913443]  smbdirect_socket_release+0x124/0x230
[ 4758.913451]  ksmbd_rdma_stop_listening+0x9f/0x190
[ 4758.913457]  ksmbd_conn_transport_destroy+0x65/0x3c0
[ 4758.913463]  kill_server_store+0x1fb/0x2b0
[ 4758.913501]  kernfs_fop_write_iter+0x349/0x4d0
[ 4758.913507]  vfs_write+0x5e7/0xc70
[…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-90171</guid>
    </item>
    <item>
      <title>GHSA-f5r6-6w97-7r58</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-f5r6-6w97-7r58</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: smbdirect: release pending child sockets outside the handler lock&lt;/p&gt;
&lt;p&gt;smbdirect_socket_destroy() releases the listener&amp;#39;s pending/ready child
sockets while still holding the listener&amp;#39;s handler lock, the
&amp;amp;id_priv-&amp;gt;handler_mutex taken via rdma_lock_handler(), not
sc-&amp;gt;listen.lock, and before the listener&amp;#39;s own rdma_destroy_id().
That ordering has one real consequence and one cosmetic one.&lt;/p&gt;
&lt;p&gt;The real one: smbdirect_socket_release() drops the child&amp;#39;s last
reference, which destroys the child&amp;#39;s cm_id.  Doing that before the
listener&amp;#39;s rdma_destroy_id() lets _cma_cancel_listens(), running from
the listener&amp;#39;s _destroy_id(), walk an already freed child id_priv,
which KASAN catches as a slab-use-after-free during listener shutdown:&lt;/p&gt;
&lt;p&gt;[ 4758.909130] BUG: KASAN: slab-use-after-free in __mutex_lock+0x1469/0x1560
[ 4758.911450] Read of size 1 at addr ffff88821c381db4 by task ksmbd.control/1652
[ 4758.913262] Call Trace:
[ 4758.913267]  &amp;lt;TASK&amp;gt;
[ 4758.913299]  __mutex_lock+0x1469/0x1560
[ 4758.913408]  _cma_cancel_listens+0x312/0x3b0
[ 4758.913413]  _destroy_id+0x363/0xee0
[ 4758.913417]  smbdirect_socket_destroy_sync+0x17d5/0x2440
[ 4758.913443]  smbdirect_socket_release+0x124/0x230
[ 4758.913451]  ksmbd_rdma_stop_listening+0x9f/0x190
[ 4758.913457]  ksmbd_conn_transport_destroy+0x65/0x3c0
[ 4758.913463]  kill_server_store+0x1fb/0x2b0
[ 4758.913501]  kernfs_fop_write_iter+0x349/0x4d0
[ 4758.913507]  vfs_write+0x5e7/0xc70
[…&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;smb: smbdirect: release pending child sockets outside the handler lock&lt;/p&gt;
&lt;p&gt;smbdirect_socket_destroy() releases the listener&amp;#39;s pending/ready child
sockets while still holding the listener&amp;#39;s handler lock, the
&amp;amp;id_priv-&amp;gt;handler_mutex taken via rdma_lock_handler(), not
sc-&amp;gt;listen.lock, and before the listener&amp;#39;s own rdma_destroy_id().
That ordering has one real consequence and one cosmetic one.&lt;/p&gt;
&lt;p&gt;The real one: smbdirect_socket_release() drops the child&amp;#39;s last
reference, which destroys the child&amp;#39;s cm_id.  Doing that before the
listener&amp;#39;s rdma_destroy_id() lets _cma_cancel_listens(), running from
the listener&amp;#39;s _destroy_id(), walk an already freed child id_priv,
which KASAN catches as a slab-use-after-free during listener shutdown:&lt;/p&gt;
&lt;p&gt;[ 4758.909130] BUG: KASAN: slab-use-after-free in __mutex_lock+0x1469/0x1560
[ 4758.911450] Read of size 1 at addr ffff88821c381db4 by task ksmbd.control/1652
[ 4758.913262] Call Trace:
[ 4758.913267]  &amp;lt;TASK&amp;gt;
[ 4758.913299]  __mutex_lock+0x1469/0x1560
[ 4758.913408]  _cma_cancel_listens+0x312/0x3b0
[ 4758.913413]  _destroy_id+0x363/0xee0
[ 4758.913417]  smbdirect_socket_destroy_sync+0x17d5/0x2440
[ 4758.913443]  smbdirect_socket_release+0x124/0x230
[ 4758.913451]  ksmbd_rdma_stop_listening+0x9f/0x190
[ 4758.913457]  ksmbd_conn_transport_destroy+0x65/0x3c0
[ 4758.913463]  kill_server_store+0x1fb/0x2b0
[ 4758.913501]  kernfs_fop_write_iter+0x349/0x4d0
[ 4758.913507]  vfs_write+0x5e7/0xc70
[…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-f5r6-6w97-7r58</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90171</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90171</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 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: smbdirect: release pending child sockets outside the handler lock smbdirect_socket_destroy() releases the listener&amp;#39;s pending/ready child sockets while still holding the listener&amp;#39;s handler lock, the &amp;amp;id_priv-&amp;gt;handler_mutex taken via rdma_lock_handler(), not sc-&amp;gt;listen.lock, and before the listener&amp;#39;s own rdma_destroy_id(). That ordering has one real consequence and one cosmetic one. The real one: smbdirect_socket_release() drops the child&amp;#39;s last reference, which destroys the child&amp;#39;s cm_id.  Doing that before the listener&amp;#39;s rdma_destroy_id() lets _cma_cancel_listens(), running from the listener&amp;#39;s _destroy_id(), walk an already freed child id_priv, which KASAN catches as a slab-use-after-free during listener shutdown: [ 4758.909130] BUG: KASAN: slab-use-after-free in __mutex_lock+0x1469/0x1560 [ 4758.911450] Read of size 1 at addr ffff88821c381db4 by task ksmbd.control/1652 [ 4758.913262] Call Trace: [ 4758.913267]  &amp;lt;TASK&amp;gt; [ 4758.913299]  __mutex_lock+0x1469/0x1560 [ 4758.913408]  _cma_cancel_listens+0x312/0x3b0 [ 4758.913413]  _destroy_id+0x363/0xee0 [ 4758.913417]  smbdirect_socket_destroy_sync+0x17d5/0x2440 [ 4758.913443]  smbdirect_socket_release+0x124/0x230 [ 4758.913451]  ksmbd_rdma_stop_listening+0x9f/0x190 [ 4758.913457]  ksmbd_conn_transport_destroy+0x65/0x3c0 [ 4758.913463]  kill_server_store+0x1fb/0x2b0 [ 4758.913501]  kernfs_fop_write_iter+0x349/0x4d0 [ 4758.913507]  vfs_write+0x5e7/0xc70 [ 4758…&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 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: smbdirect: release pending child sockets outside the handler lock smbdirect_socket_destroy() releases the listener&amp;#39;s pending/ready child sockets while still holding the listener&amp;#39;s handler lock, the &amp;amp;id_priv-&amp;gt;handler_mutex taken via rdma_lock_handler(), not sc-&amp;gt;listen.lock, and before the listener&amp;#39;s own rdma_destroy_id(). That ordering has one real consequence and one cosmetic one. The real one: smbdirect_socket_release() drops the child&amp;#39;s last reference, which destroys the child&amp;#39;s cm_id.  Doing that before the listener&amp;#39;s rdma_destroy_id() lets _cma_cancel_listens(), running from the listener&amp;#39;s _destroy_id(), walk an already freed child id_priv, which KASAN catches as a slab-use-after-free during listener shutdown: [ 4758.909130] BUG: KASAN: slab-use-after-free in __mutex_lock+0x1469/0x1560 [ 4758.911450] Read of size 1 at addr ffff88821c381db4 by task ksmbd.control/1652 [ 4758.913262] Call Trace: [ 4758.913267]  &amp;lt;TASK&amp;gt; [ 4758.913299]  __mutex_lock+0x1469/0x1560 [ 4758.913408]  _cma_cancel_listens+0x312/0x3b0 [ 4758.913413]  _destroy_id+0x363/0xee0 [ 4758.913417]  smbdirect_socket_destroy_sync+0x17d5/0x2440 [ 4758.913443]  smbdirect_socket_release+0x124/0x230 [ 4758.913451]  ksmbd_rdma_stop_listening+0x9f/0x190 [ 4758.913457]  ksmbd_conn_transport_destroy+0x65/0x3c0 [ 4758.913463]  kill_server_store+0x1fb/0x2b0 [ 4758.913501]  kernfs_fop_write_iter+0x349/0x4d0 [ 4758.913507]  vfs_write+0x5e7/0xc70 [ 4758…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90171</guid>
    </item>
  </channel>
</rss>
