CVE-2026-23367
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…
Does this matter?
Lower severity and a low EPSS score (0.12%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.12% probability · 2th percentile
- CISA KEV
- Not listed
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/129c8bb320a7cef692c78056ef8e89a2a12ba448Patch
- https://git.kernel.org/stable/c/2a60c588d5d39ad187628f58395c776a97fd4323Patch
- https://git.kernel.org/stable/c/2f8ceeba670610d66f77def32011f48de951d781Patch
- https://git.kernel.org/stable/c/6f80f6a60f5d87e5de5fb2732751fce799991c24Patch
- https://git.kernel.org/stable/c/703fa979badbba83d31cd011606d060bfb8b0d1dPatch
- https://git.kernel.org/stable/c/c854758abe0b8d86f9c43dc060ff56a0ee5b31e0Patch
- https://git.kernel.org/stable/c/d1d1d3c50095928624a95b67a6d7ccc3a18f2215Patch
- https://git.kernel.org/stable/c/e664971759a0e5570b50c6592e58a7f97d55e992Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.