GHSA-C2F5-4C4Q-2G8J
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: fix non-AQL packet accounting for MLO stations
__mt76_tx_queue_skb() overrides the wcid passed by the driver with sta->drv_priv, so the wcid might incorrectly be changed after TX, causing wcid->non_aql_packets to be counted on the wrong wcid. For example, on the AP side, if a station's setup link is the 5G link and the station uses 2G to transmit a frame, the value of non_aql_packets is increased on the 5G wcid but decreased on the 2G wcid. Once the inflated counter exceeds MT_MAX_NON_AQL_PKT, the TX scheduler permanently refuses to service the station.
Drop the reassignment and account on the wcid used for transmission. This also records the actual wcid in the queue entry.
{
"affected": [],
"aliases": [
"CVE-2026-90375"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:36Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: fix non-AQL packet accounting for MLO stations\n\n__mt76_tx_queue_skb() overrides the wcid passed by the driver with\nsta-\u003edrv_priv, so the wcid might incorrectly be changed after TX,\ncausing wcid-\u003enon_aql_packets to be counted on the wrong wcid. For\nexample, on the AP side, if a station\u0027s setup link is the 5G link and\nthe station uses 2G to transmit a frame, the value of non_aql_packets\nis increased on the 5G wcid but decreased on the 2G wcid. Once the\ninflated counter exceeds MT_MAX_NON_AQL_PKT, the TX scheduler\npermanently refuses to service the station.\n\nDrop the reassignment and account on the wcid used for transmission.\nThis also records the actual wcid in the queue entry.",
"id": "GHSA-c2f5-4c4q-2g8j",
"modified": "2026-09-17T18:32:03Z",
"published": "2026-09-17T18:32:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90375"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/186c957ac3325aefb982567ffdd3654b283688a7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8ae659743ba936b22ecb4620815887728e2820d6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f85f6933cc170155f1c7c2dffdd014965787c71b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fc7fae55255ccbde009232e84b102d2782a69ecf"
}
],
"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.