CVE-2025-21909
What it is
In the Linux kernel, the following vulnerability has been resolved: wifi: nl80211: reject cooked mode if it is set along with other flags It is possible to set both MONITOR_FLAG_COOK_FRAMES and MONITOR_FLAG_ACTIVE flags simultaneously on the same monitor interface from the userspace. This causes a sub-interface to be created with no IEEE80211_SDATA_IN_DRIVER bit set because the monitor interface is in the cooked state and it takes precedence over all other states. When the interface is then being deleted the kernel calls WARN_ONCE() from check_sdata_in_driver() because of missing that bit. Fix this by rejecting MONITOR_FLAG_COOK_FRAMES if it is set along with other flags. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- Linux Kernel < 5.4.291
- Linux Kernel < 5.10.235
- Linux Kernel < 5.15.179
- Linux Kernel < 6.1.131
- Linux Kernel < 6.6.83
- Linux Kernel < 6.12.19
- Linux Kernel < 6.13.7
- Linux Kernel 6.14
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-21909.md and follow it. Check whether this project is affected by CVE-2025-21909. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/236f41ca728f23210b31ed2d1d8a6df575a4b2d6
- https://git.kernel.org/stable/c/351eb7ac53ff1cd94d893c0c4534ced2f36ae7d7
- https://git.kernel.org/stable/c/49f27f29446a5bfe633dd2cc0cfebd48a1a5e77f
- https://git.kernel.org/stable/c/521e55c2b0d6028861ac0a2d06aa57bb0e3ac486
- https://git.kernel.org/stable/c/5ea856d93794c4afa5542defd8c61f2708dc245a
- https://git.kernel.org/stable/c/ac4860141300581d3e2f6c6dafa37220f7ea9f65
- https://git.kernel.org/stable/c/cd1bdcb77fdc03c253137e55bae10551b3481461
- https://git.kernel.org/stable/c/ebebbb0eded2ed9a1abfa31962f6fb699e6abce7
References
- https://git.kernel.org/stable/c/236f41ca728f23210b31ed2d1d8a6df575a4b2d6
- https://git.kernel.org/stable/c/351eb7ac53ff1cd94d893c0c4534ced2f36ae7d7
- https://git.kernel.org/stable/c/49f27f29446a5bfe633dd2cc0cfebd48a1a5e77f
- https://git.kernel.org/stable/c/521e55c2b0d6028861ac0a2d06aa57bb0e3ac486
- https://git.kernel.org/stable/c/5ea856d93794c4afa5542defd8c61f2708dc245a
- https://git.kernel.org/stable/c/ac4860141300581d3e2f6c6dafa37220f7ea9f65
- https://git.kernel.org/stable/c/cd1bdcb77fdc03c253137e55bae10551b3481461
- https://git.kernel.org/stable/c/ebebbb0eded2ed9a1abfa31962f6fb699e6abce7
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html