<?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-24T11:58:35.280968+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-98870</id>
    <title>fkie_cve-2026-98870</title>
    <updated>2026-10-24T11:58:35.305231+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>ksmbd: remove stale channels from all sessions on teardown</p>
<p>ksmbd_sessions_deregister() removes a connection's channels from other
sessions' channel lists only while conn-&gt;binding is still set:</p>
<p>if (conn-&gt;binding) {
		hash_for_each_safe(sessions_table, ...)
			ksmbd_chann_del(conn, sess);
	}</p>
<p>conn-&gt;binding is a transient flag: it is cleared once a binding
SESSION_SETUP completes, and also by a subsequent non-binding
SESSION_SETUP on the same connection (a reauthentication on a bound
channel, or a new SessionId==0 setup). A connection that has bound a
channel into another session's ksmbd_chann_list and then clears
conn-&gt;binding leaves that channel behind when it disconnects: the
channel, whose chann-&gt;conn points at the now freed struct ksmbd_conn,
stays on the owner session's list.</p>
<p>When the owning connection later tears down, the second loop
dereferences the stale channel:</p>
<p>xa_for_each(&amp;sess-&gt;ksmbd_chann_list, chann_id, chann)
		if (chann-&gt;conn != conn)
			ksmbd_conn_set_exiting(chann-&gt;conn);   /* freed */</p>
<p>which is a use-after-free write into the freed ksmbd_conn (the same
stale channel is also walked by show_proc_session() through /proc). The
session is leaked as well, because its channel list never empties.</p>
<p>Remove the conn-&gt;binding gate so a connection always removes its
channels from every session on teardown.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98870"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-wr5r-399q-pwfr</id>
    <title>GHSA-wr5r-399q-pwfr</title>
    <updated>2026-10-24T11:58:35.305491+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>ksmbd: remove stale channels from all sessions on teardown</p>
<p>ksmbd_sessions_deregister() removes a connection's channels from other
sessions' channel lists only while conn-&gt;binding is still set:</p>
<p>if (conn-&gt;binding) {
		hash_for_each_safe(sessions_table, ...)
			ksmbd_chann_del(conn, sess);
	}</p>
<p>conn-&gt;binding is a transient flag: it is cleared once a binding
SESSION_SETUP completes, and also by a subsequent non-binding
SESSION_SETUP on the same connection (a reauthentication on a bound
channel, or a new SessionId==0 setup). A connection that has bound a
channel into another session's ksmbd_chann_list and then clears
conn-&gt;binding leaves that channel behind when it disconnects: the
channel, whose chann-&gt;conn points at the now freed struct ksmbd_conn,
stays on the owner session's list.</p>
<p>When the owning connection later tears down, the second loop
dereferences the stale channel:</p>
<p>xa_for_each(&amp;sess-&gt;ksmbd_chann_list, chann_id, chann)
		if (chann-&gt;conn != conn)
			ksmbd_conn_set_exiting(chann-&gt;conn);   /* freed */</p>
<p>which is a use-after-free write into the freed ksmbd_conn (the same
stale channel is also walked by show_proc_session() through /proc). The
session is leaked as well, because its channel list never empties.</p>
<p>Remove the conn-&gt;binding gate so a connection always removes its
channels from every session on teardown.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-wr5r-399q-pwfr"/>
  </entry>
</feed>
