CVE-2026-99777net/9p/usbg: remove bogus context initialization in alloc_requests
- —Not scoredno CVSS score yet
- —Exploitation in 30 daysno EPSS score yet
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 56 days later
· 56 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE.
- EPSS (exploitation in 30 days)
- Not scored
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected a3be076dc174d9022a71a12554feb4c97b5c4d5c – < 3bd662cdf7d18d12be2c6010fe4049b02763d8ec
- affected a3be076dc174d9022a71a12554feb4c97b5c4d5c – < 591939db7cff9ca80a5a5deb2e3371b731817ac4
- affected a3be076dc174d9022a71a12554feb4c97b5c4d5c – < b3d262be54f5cfc5f75f7271e94d64a6315cd2f1
- affected a3be076dc174d9022a71a12554feb4c97b5c4d5c – < bbdb38b2e543ffa72dca5450f2535cf998ef1cdd
- affected 6.12
- unaffected < 6.12
- unaffected 6.12.118 – ≤ 6.12.*
- unaffected 6.18.64 – ≤ 6.18.*
- unaffected 7.3.5 – ≤ 7.3.*
- unaffected 7.4-rc2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/3bd662cdf7d18d12be2c6010fe4049b02763d8ec (opens in a new tab)
- https://git.kernel.org/stable/c/591939db7cff9ca80a5a5deb2e3371b731817ac4 (opens in a new tab)
- https://git.kernel.org/stable/c/b3d262be54f5cfc5f75f7271e94d64a6315cd2f1 (opens in a new tab)
- https://git.kernel.org/stable/c/bbdb38b2e543ffa72dca5450f2535cf998ef1cdd (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99777)Record last updated .