GHSA-8JH2-32H2-GRWF
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7996: fix TX DMA mapping leak for AddBA req frames
mt7996/mt7992 hand the firmware a HW MAC-TXP for AddBA req action frames (MT_TXD7_MAC_TXD, set in mt7996_mac_write_txwi_80211()), but are otherwise FW-TXP devices. On tx free mt76_connac_txp_skb_unmap() therefore decodes the per-frame txp as a struct mt76_connac_fw_txp. For a MAC-TXP the fw_txp.nbuf byte aliases the AddBA TID word (MT_TXP1_TID_ADDBA), which is always zero, so the unmap loop runs zero times and the skb DMA mapping in buf[1] is never unmapped. buf[1].skip_unmap is set unconditionally, so the generic DMA-ring cleanup skips it as well.
Each AddBA req therefore leaks one TX DMA mapping, roughly one per (re)association. With WED enabled these mappings are bounced through the WED swiotlb pool, so under continuous client reconnect churn the pool is exhausted after ~1-2 days, after which DMA mapping fails for WED, the WiFi MCU and other on-SoC consumers.
Keep the deferred (token release) unmap that the design relies on, and add an mt7996-specific txp unmap that inspects MT_TXD7_MAC_TXD and unmaps buf[1] from the MAC-TXP layout for those frames, delegating to mt76_connac_txp_skb_unmap() otherwise.
{
"affected": [],
"aliases": [
"CVE-2026-80934"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:18:57Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7996: fix TX DMA mapping leak for AddBA req frames\n\nmt7996/mt7992 hand the firmware a HW MAC-TXP for AddBA req action frames\n(MT_TXD7_MAC_TXD, set in mt7996_mac_write_txwi_80211()), but are otherwise\nFW-TXP devices. On tx free mt76_connac_txp_skb_unmap() therefore decodes\nthe per-frame txp as a struct mt76_connac_fw_txp. For a MAC-TXP the\nfw_txp.nbuf byte aliases the AddBA TID word (MT_TXP1_TID_ADDBA), which is\nalways zero, so the unmap loop runs zero times and the skb DMA mapping in\nbuf[1] is never unmapped. buf[1].skip_unmap is set unconditionally, so the\ngeneric DMA-ring cleanup skips it as well.\n\nEach AddBA req therefore leaks one TX DMA mapping, roughly one per\n(re)association. With WED enabled these mappings are bounced through the\nWED swiotlb pool, so under continuous client reconnect churn the pool is\nexhausted after ~1-2 days, after which DMA mapping fails for WED, the WiFi\nMCU and other on-SoC consumers.\n\nKeep the deferred (token release) unmap that the design relies on, and add\nan mt7996-specific txp unmap that inspects MT_TXD7_MAC_TXD and unmaps\nbuf[1] from the MAC-TXP layout for those frames, delegating to\nmt76_connac_txp_skb_unmap() otherwise.",
"id": "GHSA-8jh2-32h2-grwf",
"modified": "2026-09-11T21:31:19Z",
"published": "2026-09-11T21:31:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80934"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/01f2e0da8548f82d704b65b513026cfedc5f8962"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b754d3a6d44c53d9853eba374d8a7ef279a9d00a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/deaa2e3656937fbbe312f0ee2616c756c6e2511f"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.