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

Published Mar 25, 2026
·
Updated

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->nextnsdata 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->nextnsdata only for vendor namespaces, even in case undefined fields are present.

Affected Software

19 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.126.1-1
Linux Linux kernel>=2.6.34.1<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.167
Linux Linux kernel>=6.2<6.6.130
Linux Linux kernel>=6.7<6.12.77
Linux Linux kernel>=6.13<6.18.17
Linux Linux kernel>=6.19<6.19.7
Linux Linux kernel=2.6.34
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
Microsoft azl3 kernel 6.6.126.1-1<6.6.130.1-1
6.6.130.1-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.130.1-1
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  3. Configuration

    Move rejection of unknown radiotap fields to after the in-namespace lookup, so iterator->_next_ns_data is used only for vendor namespaces and undefined fields such as field 18 are rejected safely.

    Linux kernel radiotap parser rejection of unknown radiotap fields = reject before using unknown field alignment/size

Event History

Mar 25, 2026
CVE Published
via MITRE·10:27 AM
Data Sourced
via MITRE·10:27 AM
Description
Data Sourced
via NVD·11:16 AM
RemedyDescriptionSeverityAffected Software
Mar 26, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-23367?

CVE-2026-23367 is classified as a medium severity vulnerability in the Linux kernel.

2

How do I fix CVE-2026-23367?

To fix CVE-2026-23367, upgrade to the latest version of the Linux kernel that includes the patch for this vulnerability.

3

What type of vulnerability is CVE-2026-23367?

CVE-2026-23367 is a denial-of-service vulnerability related to the radiotap parser in the Linux kernel.

4

Who is affected by CVE-2026-23367?

CVE-2026-23367 affects users of the Linux kernel that utilize the radiotap parser for wireless communication.

5

What does CVE-2026-23367 specifically address?

CVE-2026-23367 addresses the handling of radiotap packets with unknown bits, which could lead to potential denial-of-service conditions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203