HIGH Introduced in 2.6.24
mac80211 MonitorMode OOB
CVE-2026-98810
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
01Description
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix slab-out-of-bounds read in ieee80211_monitor_select_queue() ieee80211_monitor_select_queue() validates the skb length using skb->len before dereferencing pointers into skb->data to access the 802.11 header. However, skb->len includes data in both the linear head buffer and non-linear fragments/pages. When AF_PACKET sends a packet large enough to become non-linear, the 802.11 header at skb->data + len_rthdr may extend past the linear head buffer even though skb->len appears sufficient. This leads to a slab-out-of-bounds read when accessing hdr->frame_control, as the kernel reads beyond the allocated skb head buffer: BUG: KASAN: slab-out-of-bounds in ieee80211_monitor_select_queue+0x1ed/0x220 syzbot has hit the same issues. Fix this by checking skb_headlen(skb) (which gives the length of the linear data region) instead of skb->len before dereferencing skb->data pointers. This ensures the required bytes are actually present in the linear portion of the skb. Apply the same fix to ieee80211_validate_radiotap_len() which has the same class of bug: it uses skb->len to validate accesses to skb->data, and to the corresponding checks in ieee80211_monitor_start_xmit(): for drivers advertising NETIF_F_SG the skb is not linearized before ndo_start_xmit, so the 802.11 header can be read past the linear buffer there as well.
02KernelScan AI Analysis
Risk summary
A local attacker with access to a wireless interface in monitor mode can trigger an out-of-bounds read in the kernel's mac80211 subsystem by injecting a large packet that becomes non-linear (scatter-gather). This leaks kernel heap memory and can cause a kernel panic, leading to both information disclosure and denial of service.
Vulnerability analysis
The mac80211 monitor mode packet injection path validates incoming packets using the total skb length (skb->len) before accessing the 802.11 header at a calculated offset within skb->data. However, skb->len includes both the linear head buffer and any fragmented pages. When AF_PACKET transmits a packet large enough to be split across fragments, the 802.11 header can straddle or fall entirely outside the linear head region even though the total length check passes. The kernel then reads the frame_control field past the allocated head buffer, causing a slab-out-of-bounds read detected by KASAN. The fix replaces all skb->len checks with skb_headlen(skb) in ieee80211_monitor_select_queue(), ieee80211_validate_radiotap_len(), and ieee80211_monitor_start_xmit(), ensuring the required header bytes are physically present in the linear data area before dereferencing. An attacker needs local access to open an AF_PACKET socket on a monitor-mode wireless interface (typically requiring CAP_NET_ADMIN or equivalent), making this reachable by unprivileged code inside a user namespace that grants that capability, as well as by any local user with access to the wireless device.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 7.2 | 2.6.24 | 7.2.10 | 63e7064b4c1c |
| mainline | 2.6.24 | 7.3 | 6f63e919fe1e |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Affected — no CIP fix yet (latest 6.12.114-cip34) |
| cip/6.1 | Affected — no CIP fix yet (latest 6.1.190-cip62) |
| cip/6.1-rt | Affected — no CIP fix yet (latest 6.1.189-cip61-rt32) |
| cip/5.10 | Affected — no CIP fix yet (latest 5.10.272-cip79) |
| cip/5.10-rt | Affected — no CIP fix yet (latest 5.10.272-cip79-rt35) |
| cip/4.19 | Affected — no CIP fix yet (latest 4.19.325-cip136) |
| cip/4.19-rt | Affected — no CIP fix yet (latest 4.19.325-cip136-rt50) |
| cip/4.4 | Affected — no CIP fix yet (latest 4.4.302-cip115) |
| cip/4.4-rt | Affected — no CIP fix yet (latest 4.4.302-cip115-rt63) |