Linux kernel 9p USB gadget driver typeconfusion memory corruption
CVE-2026-99777 Published on November 20, 2026
net/9p/usbg: remove bogus context initialization in alloc_requests
In the Linux kernel, the following vulnerability has been resolved:
net/9p/usbg: remove bogus context initialization in alloc_requests
alloc_requests() initializes usb9pfs->in_req->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->context only ever holds a valid p9_req_t once a request has
actually been queued.
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->t_err = -ECONNRESET) and
hands it to p9_client_cb(), which manipulates req->wq and req->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.
usb9pfs->out_req->context is set the same way but is never read by
this transport (usb9pfs_rx_complete() identifies the instance via
ep->driver_data instead), so it serves no purpose either.
Both endpoints' ->driver_data are already set to usb9pfs in
enable_endpoint(), which is what the completion handlers actually use
to recover the f_usb9pfs instance. Just drop the leftover
->context assignments; usb_ep_alloc_request()/alloc_ep_req() already
return zeroed requests, so in_req->context correctly starts out NULL.
Products Associated with CVE-2026-99777
Want to know whenever a new CVE is published for Linux Kernel? stack.watch will email you.
Affected Versions
Linux:- Version a3be076dc174d9022a71a12554feb4c97b5c4d5c and below 3bd662cdf7d18d12be2c6010fe4049b02763d8ec is affected.
- Version a3be076dc174d9022a71a12554feb4c97b5c4d5c and below 591939db7cff9ca80a5a5deb2e3371b731817ac4 is affected.
- Version a3be076dc174d9022a71a12554feb4c97b5c4d5c and below b3d262be54f5cfc5f75f7271e94d64a6315cd2f1 is affected.
- Version a3be076dc174d9022a71a12554feb4c97b5c4d5c and below bbdb38b2e543ffa72dca5450f2535cf998ef1cdd is affected.
- Version 6.12 is affected.
- Before 6.12 is unaffected.
- Version 6.12.118, <= 6.12.* is unaffected.
- Version 6.18.64, <= 6.18.* is unaffected.
- Version 7.3.5, <= 7.3.* is unaffected.
- Version 7.4-rc2, <= * is unaffected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.