wifi: nl80211: reject cooked mode if it is set along with other flags
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 66f7ac50ed7cc5c19a62bc97e8f6e7891004a03a · < 521e55c2b0d6028861ac0a2d06aa57bb0e3ac486| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s nl80211 interface can accept cooked and active monitor flags together on one Wi-Fi monitor interface. A local userspace process that sets both flags can trigger a kernel warning when the interface is deleted; the input does not specify authentication or privilege requirements.
Administrators running Linux kernels with the affected nl80211 behavior should check their versions; no affected version range is provided.