Kernel warning via conflicting monitor-mode flags
Published Apr 1, 2025 · Updated May 11, 2026
Improper nl80211 flag validation in Linux allows local users to trigger a kernel warning by creating and deleting a monitor interface. Cooked mode takes precedence over active mode, leaving the sub-interface without IEEE80211_SDATA_IN_DRIVER before check_sdata_in_driver() examines it during deletion. The path requires low-privileged local access and a wireless monitor interface; the published record establishes WARN_ONCE(), not a crash or hang.
Summary
What happened
Improper nl80211 flag validation in Linux allows local users to trigger a kernel warning by creating and deleting a monitor interface. Cooked mode takes precedence over active mode, leaving the sub-interface without IEEE80211_SDATA_IN_DRIVER before check_sdata_in_driver() examines it during deletion. The path requires low-privileged local access and a wireless monitor interface; the published record establishes WARN_ONCE(), not a crash or hang.
The record
- CVE
- CVE-2025-21909
- Published
- Apr 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.26
- Affected versionversion=66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a <236f41ca728f23210b31ed2d1d8a6df575a4b2d6
- Affected versionversion=66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a <351eb7ac53ff1cd94d893c0c4534ced2f36ae7d7
- Affected versionversion=66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a <49f27f29446a5bfe633dd2cc0cfebd48a1a5e77f
- Affected versionversion=66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a <521e55c2b0d6028861ac0a2d06aa57bb0e3ac486
- Affected versionversion=66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a <5ea856d93794c4afa5542defd8c61f2708dc245a
- Affected versionversion=66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a <ac4860141300581d3e2f6c6dafa37220f7ea9f65
- Affected versionversion=66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a <cd1bdcb77fdc03c253137e55bae10551b3481461
- Affected versionversion=66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a <ebebbb0eded2ed9a1abfa31962f6fb699e6abce7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo