Linux
wifi: libipw: reject too-short beacon and probe responses
In the Linux kernel, the following vulnerability has been resolved: wifi: libipw: reject too-short beacon and probe responses libipw_process_probe_response() and the libipw_network_init() call it makes assume the frame contains the full 36-byte beacon and probe response prefix, but the ipw2100 and ipw2200 receive paths only establish that a management frame carries the generic 24-byte three-address header. libipw_network_init() then computes the information element length as stats->len - sizeof(*beacon) stats->len is a u16 and sizeof() has type size_t, so the subtraction is evaluated as size_t and wraps instead of going negative. Truncating that to the u16 length parameter of libipw_parse_info_param() yields 65524 for a 24-byte beacon, and the parser then walks the receive buffer as if it held almost 64 KiB of information elements, reading past the allocation. Reject the frame before any fixed field is touched. Found by an AI-assisted review of length arithmetic in management frame parsers. Verified with a KUnit case under Generic KASAN on arm64 under QEMU; I do not have the hardware, so it is not tested on a real device.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= b453872c35cfcbdbf5a794737817f7d4e7b1b579, < cee6f141b3bebe62eb0363fd147acb52023935f0
- >= b453872c35cfcbdbf5a794737817f7d4e7b1b579, < 23afeb5d2bdfd34c8a0a661876291a4fa9978293
- >= b453872c35cfcbdbf5a794737817f7d4e7b1b579, < 89959ff00a978f3172726d3d5f861ee6f1aae26d
- >= b453872c35cfcbdbf5a794737817f7d4e7b1b579, < 14ae269c1306053ddf1ccf37c4bd66e085a652d1
- >= b453872c35cfcbdbf5a794737817f7d4e7b1b579, < ff756e6647722b7d225d882f7bdb186d8eee318e
- >= b453872c35cfcbdbf5a794737817f7d4e7b1b579, < 2c87bbc00dc93149d1dc4f803ad92d92e4ef3758
- >= b453872c35cfcbdbf5a794737817f7d4e7b1b579, < 19959fb60228f6dccc40d55507f8b1a751c2dc89
- >= b453872c35cfcbdbf5a794737817f7d4e7b1b579, < 5ce5721e8cbe3e80db8f43851cc2a2a92485ef4b
Fixed in cee6f141b3bebe62eb0363fd147acb52023935f0, 23afeb5d2bdfd34c8a0a661876291a4fa9978293, 89959ff00a978f3172726d3d5f861ee6f1aae26d, 14ae269c1306053ddf1ccf37c4bd66e085a652d1, ff756e6647722b7d225d882f7bdb186d8eee318e, 2c87bbc00dc93149d1dc4f803ad92d92e4ef3758, 19959fb60228f6dccc40d55507f8b1a751c2dc89, 5ce5721e8cbe3e80db8f43851cc2a2a92485ef4b
- 2.6.14
Fixed in 0, 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8, 7.3
Mitigation
Upgrade Linux to cee6f141b3bebe62eb0363fd147acb52023935f0 or 23afeb5d2bdfd34c8a0a661876291a4fa9978293 or 89959ff00a978f3172726d3d5f861ee6f1aae26d or 14ae269c1306053ddf1ccf37c4bd66e085a652d1 or ff756e6647722b7d225d882f7bdb186d8eee318e or 2c87bbc00dc93149d1dc4f803ad92d92e4ef3758 or 19959fb60228f6dccc40d55507f8b1a751c2dc89 or 5ce5721e8cbe3e80db8f43851cc2a2a92485ef4b or later.
Upgrade Linux to 0 or 5.10.271 or 5.15.222 or 6.1.189 or 6.6.158 or 6.12.112 or 6.18.54 or 7.2.8 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.