wifi: radiotap: reject radiotap with unknown bits
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 33e5a2f776e331dc8a4379b6efb660d38f182d96 · < 2f8ceeba670610d66f77def32011f48de951d781| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: radiotap: reject radiotap with unknown bits
The radiotap parser is currently only used with the radiotap namespace (not with vendor namespaces), but if the undefined field 18 is used, the alignment/size is unknown as well. In this case, iterator->_next_ns_data isn't initialized (it's only set for skipping vendor namespaces), and syzbot points out that we later compare against this uninitialized value.
Fix this by moving the rejection of unknown radiotap fields down to after the in-namespace lookup, so it will really use iterator->_next_ns_data only for vendor namespaces, even in case undefined fields are present.
From the CVE record · Linux
The Linux kernel radiotap parser can compare an uninitialized value when a radiotap field uses undefined bit 18. The input does not establish whether an attacker can trigger this over a network or locally, or whether authentication or user interaction is required.
Engineers running Linux kernels with the affected radiotap parser should check their kernel version; affected versions are not specified.