KernelScan.io

HIGH Introduced in 3.9

iwlwifi TxResp OOB

CVE-2026-93793

CVSS 8.8 / 10.0 NVD

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

KernelScan AI8.0HIGH

01

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.

02

Engine v0.6.0

Risk summary

The Intel iwlwifi WiFi driver fails to validate the layout of firmware TX command responses before parsing them. A malicious WiFi peer within radio range could influence the firmware to produce responses with unexpected frame counts, causing the driver to read beyond the allocated response buffer. This can leak kernel memory or crash the kernel, affecting any device using affected Intel WiFi hardware.

Affecteddrivers/net/wireless/intel/iwlwifi/mvm/tx.c (iwlwifi mvm WiFi driver)

Vulnerability analysis

The WiFi driver uses a count provided by the firmware in a transmit response to walk through status entries and then read a trailing value at the end of the response. It did not verify that the response buffer was actually large enough to contain all the entries implied by that count. When the firmware supplies a larger count than the buffer can hold, the driver reads past the end of the buffer into adjacent kernel memory. The fix calculates the exact minimum size required for the reported count and discards any response that is too small. It also rejects responses with a count other than one when a newer firmware interface is in use. The bug is reached during normal wireless operation; an attacker only needs to be within radio range of a device using an affected Intel wireless adapter and can trigger it by sending crafted wireless traffic that causes the firmware to generate malformed transmit status reports.

03

BranchIntroducedFixed inPatch commit
6.123.96.12.111fc14f5fe8a43
6.183.96.18.534d942dfc13ae
6.63.96.6.1605e871c03506c
mainline3.97.28d70881707b4
cip/6.123.96.12.111-cip32fc14f5fe8a43

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.111-cip32
cip/6.1Affected — no CIP fix yet (latest 6.1.189-cip61)
cip/6.1-rtAffected — no CIP fix yet (latest 6.1.189-cip61-rt32)
cip/5.10Affected — no CIP fix yet (latest 5.10.271-cip78)
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.268-cip77-rt34)
cip/4.19Affected — no CIP fix yet (latest 4.19.325-cip136)
cip/4.19-rtAffected — no CIP fix yet (latest 4.19.325-cip136-rt50)
cip/4.4Affected — no CIP fix yet (latest 4.4.302-cip115)
cip/4.4-rtAffected — no CIP fix yet (latest 4.4.302-cip115-rt63)