<?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>Fri, 20 Nov 2026 21:04:46 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99539</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99539</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix session reference leak on compounded SESSION_SETUP&lt;/p&gt;
&lt;p&gt;A compound request can place SESSION_SETUP after another command. That
earlier command leaves a reference to its session in work-&amp;gt;sess.
smb2_sess_setup() then overwrites work-&amp;gt;sess with the session it looks up
or creates, and the dispatcher later puts work-&amp;gt;sess only once. The
inherited reference is never dropped. That leaks the session, together
with its setup connection and socket, and every repeat of the compound
leaks another.&lt;/p&gt;
&lt;p&gt;unreferenced object (size 512):
    __kmalloc_cache_noprof+0x32c/0x3a0
    ksmbd_smb2_session_create+0xf6/0x9c0 [ksmbd]
    smb2_sess_setup+0xda4/0x6280 [ksmbd]
    handle_ksmbd_work+0x88c/0x1cb0 [ksmbd]&lt;/p&gt;
&lt;p&gt;Save the inherited session on entry. After the request has been
processed, release it once, but only when smb2_sess_setup() has replaced
work-&amp;gt;sess with its own session or cleared it. Do this after
ksmbd_conn_unlock() so the put does not run under srv_mutex. An error path
may instead leave the inherited session in work-&amp;gt;sess. Keep it there, so
the dispatcher still puts it and the error response is still signed or
encrypted with it as before.&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;ksmbd: fix session reference leak on compounded SESSION_SETUP&lt;/p&gt;
&lt;p&gt;A compound request can place SESSION_SETUP after another command. That
earlier command leaves a reference to its session in work-&amp;gt;sess.
smb2_sess_setup() then overwrites work-&amp;gt;sess with the session it looks up
or creates, and the dispatcher later puts work-&amp;gt;sess only once. The
inherited reference is never dropped. That leaks the session, together
with its setup connection and socket, and every repeat of the compound
leaks another.&lt;/p&gt;
&lt;p&gt;unreferenced object (size 512):
    __kmalloc_cache_noprof+0x32c/0x3a0
    ksmbd_smb2_session_create+0xf6/0x9c0 [ksmbd]
    smb2_sess_setup+0xda4/0x6280 [ksmbd]
    handle_ksmbd_work+0x88c/0x1cb0 [ksmbd]&lt;/p&gt;
&lt;p&gt;Save the inherited session on entry. After the request has been
processed, release it once, but only when smb2_sess_setup() has replaced
work-&amp;gt;sess with its own session or cleared it. Do this after
ksmbd_conn_unlock() so the put does not run under srv_mutex. An error path
may instead leave the inherited session in work-&amp;gt;sess. Keep it there, so
the dispatcher still puts it and the error response is still signed or
encrypted with it as before.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99539</guid>
    </item>
    <item>
      <title>GHSA-42jx-q75f-j6j5</title>
      <link>https://db.gcve.eu/vuln/ghsa-42jx-q75f-j6j5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix session reference leak on compounded SESSION_SETUP&lt;/p&gt;
&lt;p&gt;A compound request can place SESSION_SETUP after another command. That
earlier command leaves a reference to its session in work-&amp;gt;sess.
smb2_sess_setup() then overwrites work-&amp;gt;sess with the session it looks up
or creates, and the dispatcher later puts work-&amp;gt;sess only once. The
inherited reference is never dropped. That leaks the session, together
with its setup connection and socket, and every repeat of the compound
leaks another.&lt;/p&gt;
&lt;p&gt;unreferenced object (size 512):
    __kmalloc_cache_noprof+0x32c/0x3a0
    ksmbd_smb2_session_create+0xf6/0x9c0 [ksmbd]
    smb2_sess_setup+0xda4/0x6280 [ksmbd]
    handle_ksmbd_work+0x88c/0x1cb0 [ksmbd]&lt;/p&gt;
&lt;p&gt;Save the inherited session on entry. After the request has been
processed, release it once, but only when smb2_sess_setup() has replaced
work-&amp;gt;sess with its own session or cleared it. Do this after
ksmbd_conn_unlock() so the put does not run under srv_mutex. An error path
may instead leave the inherited session in work-&amp;gt;sess. Keep it there, so
the dispatcher still puts it and the error response is still signed or
encrypted with it as before.&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;ksmbd: fix session reference leak on compounded SESSION_SETUP&lt;/p&gt;
&lt;p&gt;A compound request can place SESSION_SETUP after another command. That
earlier command leaves a reference to its session in work-&amp;gt;sess.
smb2_sess_setup() then overwrites work-&amp;gt;sess with the session it looks up
or creates, and the dispatcher later puts work-&amp;gt;sess only once. The
inherited reference is never dropped. That leaks the session, together
with its setup connection and socket, and every repeat of the compound
leaks another.&lt;/p&gt;
&lt;p&gt;unreferenced object (size 512):
    __kmalloc_cache_noprof+0x32c/0x3a0
    ksmbd_smb2_session_create+0xf6/0x9c0 [ksmbd]
    smb2_sess_setup+0xda4/0x6280 [ksmbd]
    handle_ksmbd_work+0x88c/0x1cb0 [ksmbd]&lt;/p&gt;
&lt;p&gt;Save the inherited session on entry. After the request has been
processed, release it once, but only when smb2_sess_setup() has replaced
work-&amp;gt;sess with its own session or cleared it. Do this after
ksmbd_conn_unlock() so the put does not run under srv_mutex. An error path
may instead leave the inherited session in work-&amp;gt;sess. Keep it there, so
the dispatcher still puts it and the error response is still signed or
encrypted with it as before.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-42jx-q75f-j6j5</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
