CVE-2026-93790 (GCVE-0-2026-93790)
Vulnerability from cvelistv5 – Published: 2026-09-24 16:02 – Updated: 2026-10-30 12:36
VLAI
EPSS
VEX
Title
wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif
Summary
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif
mvmsta->tid_data was indexed by the TFD loop counter 'i' instead of
the actual TID value 'tid'. This writes lq_color into a random tid_data
slot unrelated to the BA entry.
Since multi-TID blockack is not really in use, 'i' was always 0 and no
harm was done.
Add a out-of-bound check before accessing the array.
Severity
8.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
41fd2fec56db2564f02532ed7244e1f69193b4ad , < ed9869e64dd7a397a320ae7a37f1e4a36f866f74
(git)
Affected: 41fd2fec56db2564f02532ed7244e1f69193b4ad , < 35f991d685feafd27255bd33272512c434e52527 (git) Affected: 41fd2fec56db2564f02532ed7244e1f69193b4ad , < c48b741277b01b2c3b4ecccedc72fc575b71dc04 (git) Affected: 41fd2fec56db2564f02532ed7244e1f69193b4ad , < e8ac5e91b1296f65c3d119fac3fa917ff458f811 (git) Affected: 41fd2fec56db2564f02532ed7244e1f69193b4ad , < 94d3982806c7f194b23484befde12934dda23064 (git) |
guessed | |
| Linux | Linux |
Affected:
4.15
Unaffected: 0 , < 4.15 (semver) Unaffected: 6.1.191 , ≤ 6.1.* (semver) Unaffected: 6.6.158 , ≤ 6.6.* (semver) Unaffected: 6.12.111 , ≤ 6.12.* (semver) Unaffected: 6.18.53 , ≤ 6.18.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/intel/iwlwifi/mvm/tx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "ed9869e64dd7a397a320ae7a37f1e4a36f866f74",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
},
{
"lessThan": "35f991d685feafd27255bd33272512c434e52527",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
},
{
"lessThan": "c48b741277b01b2c3b4ecccedc72fc575b71dc04",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
},
{
"lessThan": "e8ac5e91b1296f65c3d119fac3fa917ff458f811",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
},
{
"lessThan": "94d3982806c7f194b23484befde12934dda23064",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/intel/iwlwifi/mvm/tx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.15"
},
{
"lessThan": "4.15",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.191",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.111",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.53",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.191",
"versionStartIncluding": "4.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.158",
"versionStartIncluding": "4.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.111",
"versionStartIncluding": "4.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.53",
"versionStartIncluding": "4.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "4.15",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif\n\nmvmsta-\u003etid_data was indexed by the TFD loop counter \u0027i\u0027 instead of\nthe actual TID value \u0027tid\u0027. This writes lq_color into a random tid_data\nslot unrelated to the BA entry.\nSince multi-TID blockack is not really in use, \u0027i\u0027 was always 0 and no\nharm was done.\nAdd a out-of-bound check before accessing the array."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 8.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:A - iwl_mvm_rx_ba_notif is the BA_NOTIF (0xc5) handler reached from iwl_pcie_rx_handle_rb \u2192 iwl_mvm_rx_mq \u2192 iwl_mvm_rx_common. The OOB index is tfd_cnt from iwl_compressed_ba_notif, firmware\u2019s report of a received 802.11 Block Ack, so the triggering bytes arrive over WiFi radio range, not a routable IP protocol.\nAC:L - On the new-TX-API path, iwl_mvm_rx_ba_notif writes mvmsta-\u003etid_data[i].lq_color for i in [0, tfd_cnt) with no cap against ARRAY_SIZE(tid_data) (9). tfd_cnt is a firmware __le16 gated only by struct_size(..., tfd, tfd_cnt) versus pkt_len; a single BA_NOTIF with tfd_cnt\u003e=10 is a deterministic sync-RX write, not a race.\nPR:N - BA_NOTIF is RX_HANDLER_SYNC with no capable() or socket-cred check. iwl_mvm_sta_from_staid_rcu only needs sta_id to name a live fw_id_to_mac_id station (associated AP or client); the RF peer needs no host uid or capability.\nUI:N - iwl_mvm_rx_ba_notif runs from NAPI when firmware posts BA_NOTIF; the victim does not mount, open a file, or otherwise act to process the compressed BA once the WiFi interface already has a station.\nS:U - tid_data sits in iwl_mvm_sta inside ieee80211_sta-\u003edrv_priv; the overflow corrupts that host kernel object and adjacent heap, and does not cross a VM, IOMMU, or sandbox authority.\nC:H - Each loop stores lq_color (TX_RES_RATE_TABLE_COL_GET of tlc_rate_info) at tid_data[i]; with tfd_cnt\u003e=10 those 40-byte-strided writes leave the 9-element array, smash vif/ptk_pn, and continue into neighboring kernel objects, a memory-corruption disclosure primitive.\nI:H - The same store is a kernel OOB write: at i=9 the lq_color write lands on iwl_mvm_sta-\u003evif, and larger tfd_cnt walks ptk_pn[] and off the station object, enabling pointer corruption and control-flow hijack rather than a bounded LQ-color update.\nA:H - Corrupting vif or later heap pointers in iwl_mvm_sta makes the following iwl_mvm_tx_reclaim() (which reads mvmsta-\u003evif and tid_data[tid]) and later station use oops; an unmapped-pointer dereference in RX softirq is a host kernel crash."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-30T12:36:41.784Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/ed9869e64dd7a397a320ae7a37f1e4a36f866f74"
},
{
"url": "https://git.kernel.org/stable/c/35f991d685feafd27255bd33272512c434e52527"
},
{
"url": "https://git.kernel.org/stable/c/c48b741277b01b2c3b4ecccedc72fc575b71dc04"
},
{
"url": "https://git.kernel.org/stable/c/e8ac5e91b1296f65c3d119fac3fa917ff458f811"
},
{
"url": "https://git.kernel.org/stable/c/94d3982806c7f194b23484befde12934dda23064"
}
],
"title": "wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-93790",
"datePublished": "2026-09-24T16:02:24.091Z",
"dateReserved": "2026-09-18T17:59:28.788Z",
"dateUpdated": "2026-10-30T12:36:41.784Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-93790",
"date": "2026-11-14",
"epss": "0.00254",
"percentile": "0.1704"
},
"microsoft_vex": {
"current_release_date": "2026-10-15T02:34:41.000Z",
"cve": "CVE-2026-93790",
"id": "msrc_CVE-2026-93790",
"initial_release_date": "2026-09-28T03:58:15.000Z",
"product_status:fixed": "1",
"product_status:known_affected": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-93790.json",
"version": "3"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/intel/iwlwifi/mvm/tx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "ed9869e64dd7a397a320ae7a37f1e4a36f866f74",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
},
{
"lessThan": "35f991d685feafd27255bd33272512c434e52527",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
},
{
"lessThan": "c48b741277b01b2c3b4ecccedc72fc575b71dc04",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
},
{
"lessThan": "e8ac5e91b1296f65c3d119fac3fa917ff458f811",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
},
{
"lessThan": "94d3982806c7f194b23484befde12934dda23064",
"status": "affected",
"version": "41fd2fec56db2564f02532ed7244e1f69193b4ad",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/intel/iwlwifi/mvm/tx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.15"
},
{
"lessThan": "4.15",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.191",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.111",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.53",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"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\nwifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif\n\nmvmsta-\u003etid_data was indexed by the TFD loop counter \u0027i\u0027 instead of\nthe actual TID value \u0027tid\u0027. This writes lq_color into a random tid_data\nslot unrelated to the BA entry.\nSince multi-TID blockack is not really in use, \u0027i\u0027 was always 0 and no\nharm was done.\nAdd a out-of-bound check before accessing the array."
}
],
"id": "CVE-2026-93790",
"lastModified": "2026-10-30T13:21:02.427",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-09-24T17:17:11.710",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/35f991d685feafd27255bd33272512c434e52527"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/94d3982806c7f194b23484befde12934dda23064"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c48b741277b01b2c3b4ecccedc72fc575b71dc04"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e8ac5e91b1296f65c3d119fac3fa917ff458f811"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ed9869e64dd7a397a320ae7a37f1e4a36f866f74"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-06T02:11:27+00:00",
"cve": "CVE-2026-93790",
"id": "CVE-2026-93790",
"initial_release_date": "2026-09-24T00:00:00+00:00",
"product_status:known_affected": "161",
"product_status:known_not_affected": "42",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-93790.json",
"version": "3"
}
}
}
Loading…
Loading…
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.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.