<?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-11-20T21:22:11.244103+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/cve-2026-99539</id>
    <title>CVE-2026-99539 — ksmbd: fix session reference leak on compounded SESSION_SETUP</title>
    <updated>2026-11-20T21:22:11.246104+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ksmbd: fix session reference leak on compounded SESSION_SETUP</p>
<p>A compound request can place SESSION_SETUP after another command. That
earlier command leaves a reference to its session in work-&gt;sess.
smb2_sess_setup() then overwrites work-&gt;sess with the session it looks up
or creates, and the dispatcher later puts work-&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.</p>
<p>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]</p>
<p>Save the inherited session on entry. After the request has been
processed, release it once, but only when smb2_sess_setup() has replaced
work-&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-&gt;sess. Keep it there, so
the dispatcher still puts it and the error response is still signed or
encrypted with it as before.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99539"/>
  </entry>
</feed>
