GHSA-5VQV-JCF8-G93J
Vulnerability from github – Published: 2026-11-19 15:31 – Updated: 2026-11-19 15:31In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7996: unlink TWT flow if the MCU rejects the agreement
mt7996_mac_add_twt_setup() links a new flow into dev->twt_list before asking the MCU to add the agreement, but exits without unlinking the flow if the request fails. The flow-ID and table masks are only committed after MCU success, so the still-linked flow is invisible to the mask-gated teardown paths.
If the station retries the setup, the same slot is cleared and its embedded list node reinitialized while it is still linked, corrupting dev->twt_list. If the station disassociates instead, teardown skips the flow and station storage can be freed while the node remains linked. A later scheduling or debugfs twt_stats walk can then dereference the freed flow, resulting in a use-after-free.
Unlink the flow when the MCU rejects the agreement. This restores the list to its pre-request state while leaving the unchanged mask and agreement accounting untouched.
{
"affected": [],
"aliases": [
"CVE-2026-99451"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-19T15:17:58Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7996: unlink TWT flow if the MCU rejects the agreement\n\nmt7996_mac_add_twt_setup() links a new flow into dev-\u003etwt_list before\nasking the MCU to add the agreement, but exits without unlinking the flow\nif the request fails. The flow-ID and table masks are only committed\nafter MCU success, so the still-linked flow is invisible to the\nmask-gated teardown paths.\n\nIf the station retries the setup, the same slot is cleared and its\nembedded list node reinitialized while it is still linked, corrupting\ndev-\u003etwt_list. If the station disassociates instead, teardown skips the\nflow and station storage can be freed while the node remains linked. A\nlater scheduling or debugfs twt_stats walk can then dereference the\nfreed flow, resulting in a use-after-free.\n\nUnlink the flow when the MCU rejects the agreement. This restores the\nlist to its pre-request state while leaving the unchanged mask and\nagreement accounting untouched.",
"id": "GHSA-5vqv-jcf8-g93j",
"modified": "2026-11-19T15:31:24Z",
"published": "2026-11-19T15:31:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99451"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/022f5f8b7a0580da50fcbc34da853d03d4321fe2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/26dc15da08f15e8320514d700d6a4c449d1bb047"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/40e3d300cc7e27b12e3307099247d6c5cc1fa009"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dd0978ebf56ee9dda9fc0ff36db91511c01fa716"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.