CVE-2026-99777
Severity unknownNo known exploitationFix availablenet/9p/usbg: remove bogus context initialization in alloc_requests
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 5% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from a3be076dc174d9022a71a12554feb4c97b5c4d5c before 591939db7cff9ca80a5a5deb2e3371b731817ac4 | 591939db7cff9ca80a5a5deb2e3371b731817ac4 | CVE Program |
| Linux | Linux | from a3be076dc174d9022a71a12554feb4c97b5c4d5c before b3d262be54f5cfc5f75f7271e94d64a6315cd2f1 | b3d262be54f5cfc5f75f7271e94d64a6315cd2f1 | CVE Program |
| Linux | Linux | from a3be076dc174d9022a71a12554feb4c97b5c4d5c before bbdb38b2e543ffa72dca5450f2535cf998ef1cdd | bbdb38b2e543ffa72dca5450f2535cf998ef1cdd | CVE Program |
| Linux | Linux | from a3be076dc174d9022a71a12554feb4c97b5c4d5c before 3bd662cdf7d18d12be2c6010fe4049b02763d8ec | 3bd662cdf7d18d12be2c6010fe4049b02763d8ec | CVE Program |
| Linux | Linux | 6.12 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.5 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc2 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.12 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- 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)