CVE-2026-99777 (GCVE-0-2026-99777)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:51 – Updated: 2026-11-20 05:51| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
a3be076dc174d9022a71a12554feb4c97b5c4d5c , < 3bd662cdf7d18d12be2c6010fe4049b02763d8ec
(git)
Affected: a3be076dc174d9022a71a12554feb4c97b5c4d5c , < 591939db7cff9ca80a5a5deb2e3371b731817ac4 (git) Affected: a3be076dc174d9022a71a12554feb4c97b5c4d5c , < b3d262be54f5cfc5f75f7271e94d64a6315cd2f1 (git) Affected: a3be076dc174d9022a71a12554feb4c97b5c4d5c , < bbdb38b2e543ffa72dca5450f2535cf998ef1cdd (git) |
guessed | |
| Linux | Linux |
Affected:
6.12
Unaffected: 0 , < 6.12 (semver) Unaffected: 6.12.118 , ≤ 6.12.* (semver) Unaffected: 6.18.64 , ≤ 6.18.* (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/9p/trans_usbg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "3bd662cdf7d18d12be2c6010fe4049b02763d8ec",
"status": "affected",
"version": "a3be076dc174d9022a71a12554feb4c97b5c4d5c",
"versionType": "git"
},
{
"lessThan": "591939db7cff9ca80a5a5deb2e3371b731817ac4",
"status": "affected",
"version": "a3be076dc174d9022a71a12554feb4c97b5c4d5c",
"versionType": "git"
},
{
"lessThan": "b3d262be54f5cfc5f75f7271e94d64a6315cd2f1",
"status": "affected",
"version": "a3be076dc174d9022a71a12554feb4c97b5c4d5c",
"versionType": "git"
},
{
"lessThan": "bbdb38b2e543ffa72dca5450f2535cf998ef1cdd",
"status": "affected",
"version": "a3be076dc174d9022a71a12554feb4c97b5c4d5c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/9p/trans_usbg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.12"
},
{
"lessThan": "6.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.118",
"versionStartIncluding": "6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.64",
"versionStartIncluding": "6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc2",
"versionStartIncluding": "6.12",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/9p/usbg: remove bogus context initialization in alloc_requests\n\nalloc_requests() initializes usb9pfs-\u003ein_req-\u003econtext to point at the\nstruct f_usb9pfs instance itself. usb9pfs_queue_tx() later overwrites\nthis with the real struct p9_req_t pointer before every transmit, and\nusb9pfs_tx_complete() clears it back to NULL after each completion, so\nin_req-\u003econtext only ever holds a valid p9_req_t once a request has\nactually been queued.\n\nusb9pfs_clear_tx(), however, can run at any time (mount close, gadget\ndisable) independent of whether a request was ever queued. If it runs\nbefore the first usb9pfs_transmit(), it reads the leftover sentinel\nvalue, type-confuses the struct f_usb9pfs pointer as a struct\np9_req_t, and both writes through it (req-\u003et_err = -ECONNRESET) and\nhands it to p9_client_cb(), which manipulates req-\u003ewq and req-\u003erefcount\nat bogus offsets inside f_usb9pfs. This reliably corrupts memory or\npanics whenever the transport is torn down before any 9p request has\nbeen transmitted, e.g. mounting and immediately unmounting, or a cable\ndisconnect racing the very first request.\n\nusb9pfs-\u003eout_req-\u003econtext is set the same way but is never read by\nthis transport (usb9pfs_rx_complete() identifies the instance via\nep-\u003edriver_data instead), so it serves no purpose either.\n\nBoth endpoints\u0027 -\u003edriver_data are already set to usb9pfs in\nenable_endpoint(), which is what the completion handlers actually use\nto recover the f_usb9pfs instance. Just drop the leftover\n-\u003econtext assignments; usb_ep_alloc_request()/alloc_ep_req() already\nreturn zeroed requests, so in_req-\u003econtext correctly starts out NULL."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:51:40.898Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/3bd662cdf7d18d12be2c6010fe4049b02763d8ec"
},
{
"url": "https://git.kernel.org/stable/c/591939db7cff9ca80a5a5deb2e3371b731817ac4"
},
{
"url": "https://git.kernel.org/stable/c/b3d262be54f5cfc5f75f7271e94d64a6315cd2f1"
},
{
"url": "https://git.kernel.org/stable/c/bbdb38b2e543ffa72dca5450f2535cf998ef1cdd"
}
],
"title": "net/9p/usbg: remove bogus context initialization in alloc_requests",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99777",
"datePublished": "2026-11-20T05:51:40.898Z",
"dateReserved": "2026-09-25T10:25:14.434Z",
"dateUpdated": "2026-11-20T05:51:40.898Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99777",
"date": "2026-11-20",
"epss": "0.00157",
"percentile": "0.04929"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/9p/trans_usbg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "3bd662cdf7d18d12be2c6010fe4049b02763d8ec",
"status": "affected",
"version": "a3be076dc174d9022a71a12554feb4c97b5c4d5c",
"versionType": "git"
},
{
"lessThan": "591939db7cff9ca80a5a5deb2e3371b731817ac4",
"status": "affected",
"version": "a3be076dc174d9022a71a12554feb4c97b5c4d5c",
"versionType": "git"
},
{
"lessThan": "b3d262be54f5cfc5f75f7271e94d64a6315cd2f1",
"status": "affected",
"version": "a3be076dc174d9022a71a12554feb4c97b5c4d5c",
"versionType": "git"
},
{
"lessThan": "bbdb38b2e543ffa72dca5450f2535cf998ef1cdd",
"status": "affected",
"version": "a3be076dc174d9022a71a12554feb4c97b5c4d5c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/9p/trans_usbg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.12"
},
{
"lessThan": "6.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/9p/usbg: remove bogus context initialization in alloc_requests\n\nalloc_requests() initializes usb9pfs-\u003ein_req-\u003econtext to point at the\nstruct f_usb9pfs instance itself. usb9pfs_queue_tx() later overwrites\nthis with the real struct p9_req_t pointer before every transmit, and\nusb9pfs_tx_complete() clears it back to NULL after each completion, so\nin_req-\u003econtext only ever holds a valid p9_req_t once a request has\nactually been queued.\n\nusb9pfs_clear_tx(), however, can run at any time (mount close, gadget\ndisable) independent of whether a request was ever queued. If it runs\nbefore the first usb9pfs_transmit(), it reads the leftover sentinel\nvalue, type-confuses the struct f_usb9pfs pointer as a struct\np9_req_t, and both writes through it (req-\u003et_err = -ECONNRESET) and\nhands it to p9_client_cb(), which manipulates req-\u003ewq and req-\u003erefcount\nat bogus offsets inside f_usb9pfs. This reliably corrupts memory or\npanics whenever the transport is torn down before any 9p request has\nbeen transmitted, e.g. mounting and immediately unmounting, or a cable\ndisconnect racing the very first request.\n\nusb9pfs-\u003eout_req-\u003econtext is set the same way but is never read by\nthis transport (usb9pfs_rx_complete() identifies the instance via\nep-\u003edriver_data instead), so it serves no purpose either.\n\nBoth endpoints\u0027 -\u003edriver_data are already set to usb9pfs in\nenable_endpoint(), which is what the completion handlers actually use\nto recover the f_usb9pfs instance. Just drop the leftover\n-\u003econtext assignments; usb_ep_alloc_request()/alloc_ep_req() already\nreturn zeroed requests, so in_req-\u003econtext correctly starts out NULL."
}
],
"id": "CVE-2026-99777",
"lastModified": "2026-11-20T06:18:16.720",
"metrics": {},
"published": "2026-11-20T06:18:16.720",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/3bd662cdf7d18d12be2c6010fe4049b02763d8ec"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/591939db7cff9ca80a5a5deb2e3371b731817ac4"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b3d262be54f5cfc5f75f7271e94d64a6315cd2f1"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bbdb38b2e543ffa72dca5450f2535cf998ef1cdd"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T11:58:46+00:00",
"cve": "CVE-2026-99777",
"id": "CVE-2026-99777",
"initial_release_date": "2026-11-20T05:51:40.898000+00:00",
"product_status:known_not_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via improper context initialization in 9P USB gadget transport",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99777.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.