CVE-2026-23367
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Linux kernel radiotap parser leaves uninitialized data when encountering unknown bits, risking information disclosure or crash.
Vulnerability
Analysis
The Linux kernel's radiotap parser, used to parse radiotap headers, has a flaw where undefined field 18 (unknown bits) leads to uninitialized use of iterator->_next_ns_data. This variable is only properly set for vendor namespaces, but when an undefined field appears in the radiotap namespace, it remains uninitialized, later causing a comparison against this garbage value [1].
Exploitation
An attacker who can inject crafted radiotap headers (e.g., through crafted Wi-Fi frames) can trigger this condition. The vulnerability was discovered via syzbot, indicating it can be triggered without special privileges beyond the ability to submit radiotap data [1].
Impact
The use of uninitialized data can lead to kernel information disclosure or a denial-of-service (system crash). The exact impact is undefined behavior, but given the kernel context, it poses a risk to confidentiality and availability with a CVSS v3 base score of 5.5 (Medium).
Mitigation
The fix was applied by moving the rejection of unknown radiotap fields after the in-namespace lookup, ensuring _next_ns_data is only used for vendor namespaces. The patches are available in the stable kernel repositories [1].
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
10cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*+ 9 more
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*range: >=2.6.34.1,<5.10.253
- cpe:2.3:o:linux:linux_kernel:2.6.34:-:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*
- (no CPE)
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
8- git.kernel.org/stable/c/129c8bb320a7cef692c78056ef8e89a2a12ba448nvdPatch
- git.kernel.org/stable/c/2a60c588d5d39ad187628f58395c776a97fd4323nvdPatch
- git.kernel.org/stable/c/2f8ceeba670610d66f77def32011f48de951d781nvdPatch
- git.kernel.org/stable/c/6f80f6a60f5d87e5de5fb2732751fce799991c24nvdPatch
- git.kernel.org/stable/c/703fa979badbba83d31cd011606d060bfb8b0d1dnvdPatch
- git.kernel.org/stable/c/c854758abe0b8d86f9c43dc060ff56a0ee5b31e0nvdPatch
- git.kernel.org/stable/c/d1d1d3c50095928624a95b67a6d7ccc3a18f2215nvdPatch
- git.kernel.org/stable/c/e664971759a0e5570b50c6592e58a7f97d55e992nvdPatch
News mentions
0No linked articles in our index yet.