Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23367

wifi: radiotap: reject radiotap with unknown bits

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23367, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 33e5a2f776e331dc8a4379b6efb660d38f182d96 – < 6f80f6a60f5d87e5de5fb2732751fce799991c24
    • affected 33e5a2f776e331dc8a4379b6efb660d38f182d96 – < d1d1d3c50095928624a95b67a6d7ccc3a18f2215
    • affected 33e5a2f776e331dc8a4379b6efb660d38f182d96 – < 703fa979badbba83d31cd011606d060bfb8b0d1d
    • affected 33e5a2f776e331dc8a4379b6efb660d38f182d96 – < 129c8bb320a7cef692c78056ef8e89a2a12ba448
    • affected 33e5a2f776e331dc8a4379b6efb660d38f182d96 – < 2a60c588d5d39ad187628f58395c776a97fd4323
    • affected 33e5a2f776e331dc8a4379b6efb660d38f182d96 – < 2f8ceeba670610d66f77def32011f48de951d781
    • affected 33e5a2f776e331dc8a4379b6efb660d38f182d96 – < e664971759a0e5570b50c6592e58a7f97d55e992
    • affected 33e5a2f776e331dc8a4379b6efb660d38f182d96 – < c854758abe0b8d86f9c43dc060ff56a0ee5b31e0
  • Linux · Linux

    • affected 2.6.34
    • unaffected < 2.6.34
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23367 badge
[![CVE-2026-23367](https://cveledger.app/badge/CVE-2026-23367.svg)](https://cveledger.app/cve/CVE-2026-23367)

Record last updated .