CVE-2026-93793 (GCVE-0-2026-93793)
Vulnerability from cvelistv5 – Published: 2026-09-24 16:02 – Updated: 2026-10-30 12:36
VLAI
EPSS
VEX
Title
wifi: iwlwifi: mvm: validate TX_CMD response layout
Summary
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: validate TX_CMD response layout
TX_CMD parsing uses frame_count to walk status entries and then
read the trailing SCD SSN. Make the minimum-length check follow
that exact runtime layout calculation before parsing the payload.
For new TX API, reject TX_CMD responses with frame_count != 1 and
warn/return in the aggregation handler to document that aggregated
accounting is expected via BA notifications.
Severity
8.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c , < 658b5c00d653cdd72babc86791f6f6711190c740
(git)
Affected: 8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c , < 5e871c03506c529d5fe372d099c1ad1465c7bc38 (git) Affected: 8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c , < fc14f5fe8a4374ed1088cfbddc1dae4d16c9935b (git) Affected: 8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c , < 4d942dfc13aec393e003ab28ff58db744c26e6eb (git) Affected: 8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c , < 8d70881707b47353359df57df12f6de67fdacdd2 (git) |
guessed | |
| Linux | Linux |
Affected:
3.9
Unaffected: 0 , < 3.9 (semver) Unaffected: 6.1.191 , ≤ 6.1.* (semver) Unaffected: 6.6.160 , ≤ 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": "658b5c00d653cdd72babc86791f6f6711190c740",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"versionType": "git"
},
{
"lessThan": "5e871c03506c529d5fe372d099c1ad1465c7bc38",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"versionType": "git"
},
{
"lessThan": "fc14f5fe8a4374ed1088cfbddc1dae4d16c9935b",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"versionType": "git"
},
{
"lessThan": "4d942dfc13aec393e003ab28ff58db744c26e6eb",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"versionType": "git"
},
{
"lessThan": "8d70881707b47353359df57df12f6de67fdacdd2",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"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": "3.9"
},
{
"lessThan": "3.9",
"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.160",
"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": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.160",
"versionStartIncluding": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.111",
"versionStartIncluding": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.53",
"versionStartIncluding": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "3.9",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: validate TX_CMD response layout\n\nTX_CMD parsing uses frame_count to walk status entries and then\nread the trailing SCD SSN. Make the minimum-length check follow\nthat exact runtime layout calculation before parsing the payload.\n\nFor new TX API, reject TX_CMD responses with frame_count != 1 and\nwarn/return in the aggregation handler to document that aggregated\naccounting is expected via BA notifications."
}
],
"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 - The malformed input is a firmware TX_CMD (REPLY_TX 0x1c) notification DMA\u0027d from the Intel WiFi NIC: iwl_pcie_rx_handle() \u2192 iwl_op_mode_rx() \u2192 iwl_mvm_rx()/iwl_mvm_rx_mq() \u2192 iwl_mvm_rx_common() \u2192 RX_HANDLER(TX_CMD, iwl_mvm_rx_tx_cmd). Those bytes are not a routable IP payload; WiFi host-device range is Adjacent.\nAC:L - iwl_mvm_rx_tx_cmd() is RX_HANDLER_SYNC; a single TX_CMD whose firmware-chosen frame_count makes iwl_mvm_tx_resp_min_len() exceed iwl_rx_packet_payload_len() (or frame_count!=1 on the new TX API) is parsed immediately, with no race or victim state the sender cannot induce by posting that notification.\nPR:N - iwl_mvm_rx_common() only checks pkt_len against sizeof(struct iwl_tx_resp) then calls iwl_mvm_rx_tx_cmd() with no uid, capability, or 802.11 authentication check; TX_CMD is in no_reclaim_cmds as a ucode-originated notif. An RF-adjacent attacker needs no host account.\nUI:N - The NAPI path consumes TX_CMD automatically when firmware posts a TX completion while the interface is up; iwl_mvm_rx_tx_cmd() does not require the victim to mount, open a file, or take any extra action at trigger time.\nS:U - iwl_mvm_get_scd_ssn() and iwl_trans_reclaim() from iwl_mvm_rx_tx_cmd_single() operate on host iwlwifi RX pages and TX queues inside the same kernel authority; this is not a KVM/Xen escape or an IOMMU/DMA-boundary bypass.\nC:H - iwl_mvm_get_scd_ssn() does le32_to_cpup((__le32 *)agg_status + frame_count) with no payload check, and iwl_mvm_rx_tx_cmd_agg_dbg() walks status[frame_count] (u8, up to 255 entries). That is an out-of-bounds read past the TX_CMD into the RX page, and a poisoned SSN into iwl_trans_reclaim() is UAF-class.\nI:H - The over-read SCD SSN is passed to iwl_trans_reclaim()/iwl_pcie_reclaim(), which unmaps TFDs, NULLs txq-\u003eentries[].skb, and advances txq-\u003eread_ptr, completing in-flight TX buffers early. That is an out-of-bounds-fed free/write of live TX objects, not a bounded status update.\nA:H - iwl_pcie_reclaim() WARNs on a missing skb or cmd-queue txq_id, and an SSN whose last_to_free is not in iwl_txq_used() desynchronizes the TX ring; walking status[frame_count] past the mapped RX buffer can oops. Kernel WARN/oops or a firmware-assert restart is high availability impact."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-30T12:36:44.982Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/658b5c00d653cdd72babc86791f6f6711190c740"
},
{
"url": "https://git.kernel.org/stable/c/5e871c03506c529d5fe372d099c1ad1465c7bc38"
},
{
"url": "https://git.kernel.org/stable/c/fc14f5fe8a4374ed1088cfbddc1dae4d16c9935b"
},
{
"url": "https://git.kernel.org/stable/c/4d942dfc13aec393e003ab28ff58db744c26e6eb"
},
{
"url": "https://git.kernel.org/stable/c/8d70881707b47353359df57df12f6de67fdacdd2"
}
],
"title": "wifi: iwlwifi: mvm: validate TX_CMD response layout",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-93793",
"datePublished": "2026-09-24T16:02:26.708Z",
"dateReserved": "2026-09-18T17:59:28.789Z",
"dateUpdated": "2026-10-30T12:36:44.982Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-93793",
"date": "2026-11-14",
"epss": "0.00255",
"percentile": "0.1718"
},
"microsoft_vex": {
"current_release_date": "2026-11-07T01:45:55.000Z",
"cve": "CVE-2026-93793",
"id": "msrc_CVE-2026-93793",
"initial_release_date": "2026-09-27T23:32:44.000Z",
"product_status:fixed": "1",
"product_status:known_affected": "2",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "wifi: iwlwifi: mvm: validate TX_CMD response layout",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-93793.json",
"version": "4"
},
"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": "658b5c00d653cdd72babc86791f6f6711190c740",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"versionType": "git"
},
{
"lessThan": "5e871c03506c529d5fe372d099c1ad1465c7bc38",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"versionType": "git"
},
{
"lessThan": "fc14f5fe8a4374ed1088cfbddc1dae4d16c9935b",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"versionType": "git"
},
{
"lessThan": "4d942dfc13aec393e003ab28ff58db744c26e6eb",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"versionType": "git"
},
{
"lessThan": "8d70881707b47353359df57df12f6de67fdacdd2",
"status": "affected",
"version": "8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c",
"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": "3.9"
},
{
"lessThan": "3.9",
"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.160",
"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: validate TX_CMD response layout\n\nTX_CMD parsing uses frame_count to walk status entries and then\nread the trailing SCD SSN. Make the minimum-length check follow\nthat exact runtime layout calculation before parsing the payload.\n\nFor new TX API, reject TX_CMD responses with frame_count != 1 and\nwarn/return in the aggregation handler to document that aggregated\naccounting is expected via BA notifications."
}
],
"id": "CVE-2026-93793",
"lastModified": "2026-10-30T13:21:02.800",
"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:12.050",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4d942dfc13aec393e003ab28ff58db744c26e6eb"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5e871c03506c529d5fe372d099c1ad1465c7bc38"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/658b5c00d653cdd72babc86791f6f6711190c740"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8d70881707b47353359df57df12f6de67fdacdd2"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/fc14f5fe8a4374ed1088cfbddc1dae4d16c9935b"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-06T02:11:32+00:00",
"cve": "CVE-2026-93793",
"id": "CVE-2026-93793",
"initial_release_date": "2026-09-24T00:00:00+00:00",
"product_status:known_affected": "189",
"product_status:known_not_affected": "14",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: wifi: iwlwifi: mvm: validate TX_CMD response layout",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-93793.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.