<?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-20T20:53:04.224428+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-99777</id>
    <title>CVE-2026-99777 — net/9p/usbg: remove bogus context initialization in alloc_requests</title>
    <updated>2026-11-20T20:53:04.226289+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>net/9p/usbg: remove bogus context initialization in alloc_requests</p>
<p>alloc_requests() initializes usb9pfs-&gt;in_req-&gt;context to point at the
struct f_usb9pfs instance itself. usb9pfs_queue_tx() later overwrites
this with the real struct p9_req_t pointer before every transmit, and
usb9pfs_tx_complete() clears it back to NULL after each completion, so
in_req-&gt;context only ever holds a valid p9_req_t once a request has
actually been queued.</p>
<p>usb9pfs_clear_tx(), however, can run at any time (mount close, gadget
disable) independent of whether a request was ever queued. If it runs
before the first usb9pfs_transmit(), it reads the leftover sentinel
value, type-confuses the struct f_usb9pfs pointer as a struct
p9_req_t, and both writes through it (req-&gt;t_err = -ECONNRESET) and
hands it to p9_client_cb(), which manipulates req-&gt;wq and req-&gt;refcount
at bogus offsets inside f_usb9pfs. This reliably corrupts memory or
panics whenever the transport is torn down before any 9p request has
been transmitted, e.g. mounting and immediately unmounting, or a cable
disconnect racing the very first request.</p>
<p>usb9pfs-&gt;out_req-&gt;context is set the same way but is never read by
this transport (usb9pfs_rx_complete() identifies the instance via
ep-&gt;driver_data instead), so it serves no purpose either.</p>
<p>Both endpoints' -&gt;driver_data are already set to usb9pfs in
enable_endpoint(), which is what the completion handlers actually use
to reco…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99777"/>
  </entry>
</feed>
