GHSA-H4F8-3Q7W-49PW
Vulnerability from github – Published: 2026-10-18 18:32 – Updated: 2026-10-30 15:33In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: minstrel_ht: validate fixed rate index
The fixed_rate_idx debugfs file is a plain u32 attribute, so any value can be written to it. minstrel_ht_update_stats() then copies the value into mi->max_tp_rate[] and mi->max_prob_rate, and minstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index minstrel_mcs_groups[] (42 entries) and mi->groups[].rates[] (10 entries) with it.
Writing e.g. 65535 selects group 4095 and rate index 15, far outside both arrays. The out-of-bounds entries are dereferenced and updated as struct minstrel_rate_stats (retry counts, etc.), so the invalid index corrupts adjacent kernel memory. With CONFIG_UBSAN_BOUNDS the access is reported as an array-index-out-of-bounds in minstrel_ht_set_rate().
Only a valid group/rate pair, or U32_MAX to disable fixed rate processing, can be used safely, so reject any other value when the debugfs file is written.
The file is only reachable through a root-only debugfs mount, so this is not a privilege boundary. The out-of-bounds access is still a bug that must not be reachable through a writable debugfs attribute.
{
"affected": [],
"aliases": [
"CVE-2026-98703"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:23Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: minstrel_ht: validate fixed rate index\n\nThe fixed_rate_idx debugfs file is a plain u32 attribute, so any value\ncan be written to it. minstrel_ht_update_stats() then copies the value\ninto mi-\u003emax_tp_rate[] and mi-\u003emax_prob_rate, and\nminstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index\nminstrel_mcs_groups[] (42 entries) and mi-\u003egroups[].rates[] (10 entries)\nwith it.\n\nWriting e.g. 65535 selects group 4095 and rate index 15, far outside\nboth arrays. The out-of-bounds entries are dereferenced and updated as\nstruct minstrel_rate_stats (retry counts, etc.), so the invalid index\ncorrupts adjacent kernel memory. With CONFIG_UBSAN_BOUNDS the access is\nreported as an array-index-out-of-bounds in minstrel_ht_set_rate().\n\nOnly a valid group/rate pair, or U32_MAX to disable fixed rate\nprocessing, can be used safely, so reject any other value when the\ndebugfs file is written.\n\nThe file is only reachable through a root-only debugfs mount, so this is\nnot a privilege boundary. The out-of-bounds access is still a bug that\nmust not be reachable through a writable debugfs attribute.",
"id": "GHSA-h4f8-3q7w-49pw",
"modified": "2026-10-30T15:33:57Z",
"published": "2026-10-18T18:32:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98703"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/15fb9e3cea55fbc378261ce35a32b0f8828f0000"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/42aa9feb27b600809414a3c6b0c650bafba542a9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/43082d604a9937b94ceb2e484403956d0f363324"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/63097bf1b7f17f14bd9ffcae6590c63272da8bb0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9b685cfb5cc8ed57991b1a956b06c6658d7cf455"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/eebc70f132041b35da9ec74d5d395083125289b2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f8ab6ae1fa360b0191252677f41e781dcb0ffe6e"
}
],
"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
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.