VulnerabilityPublished 25 Mar 2026Updated 5 Nov 2026

CVE-2026-23367: Linux kernel · wifi: radiotap: reject radiotap with unknown bits

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in e664971759a0e5570b50c6592e58a7f97d55e992 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 23:24 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

EPSS

0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in e664971759a0e5570b50c6592e58a7f97d55e992, d1d1d3c50095928624a95b67a6d7ccc3a18f2215, c854758abe0b8d86f9c43dc060ff56a0ee5b31e0 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 33e5a2f776e331dc8a4379b6efb660d38f182d96, < e664971759a0e5570b50c6592e58a7f97d55e992	Fixed in e664971759a0e5570b50c6592e58a7f97d55e992
LinuxLinux	Affected ≥ 33e5a2f776e331dc8a4379b6efb660d38f182d96, < d1d1d3c50095928624a95b67a6d7ccc3a18f2215	Fixed in d1d1d3c50095928624a95b67a6d7ccc3a18f2215
LinuxLinux	Affected ≥ 33e5a2f776e331dc8a4379b6efb660d38f182d96, < c854758abe0b8d86f9c43dc060ff56a0ee5b31e0	Fixed in c854758abe0b8d86f9c43dc060ff56a0ee5b31e0
LinuxLinux	Affected ≥ 33e5a2f776e331dc8a4379b6efb660d38f182d96, < 703fa979badbba83d31cd011606d060bfb8b0d1d	Fixed in 703fa979badbba83d31cd011606d060bfb8b0d1d
LinuxLinux	Affected ≥ 33e5a2f776e331dc8a4379b6efb660d38f182d96, < 129c8bb320a7cef692c78056ef8e89a2a12ba448	Fixed in 129c8bb320a7cef692c78056ef8e89a2a12ba448
LinuxLinux	Affected ≥ 33e5a2f776e331dc8a4379b6efb660d38f182d96, < 6f80f6a60f5d87e5de5fb2732751fce799991c24	Fixed in 6f80f6a60f5d87e5de5fb2732751fce799991c24

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.

References

Community reviews

Loading reviews…