cbcvebase.
CVE-2025-71127
published 2026-01-14

CVE-2025-71127: In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required…

PriorityP422medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
10.1th percentile
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping unicast Beacon frames with Protected Frame bit 1, these frames would be accepted in mac80211 processing as valid Beacon frames even though they are not protected. This would allow beacon protection to be bypassed. While the logic for checking beacon protection could be extended to cover this corner case, a more generic check for discard all Beacon frames based on A1=unicast address covers this without needing additional changes. Address all these issues by dropping received Beacon frames if they are sent to a non-broadcast address.

Affected

68 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.162-1 (bookworm)linux 6.1.162-1 (bookworm)
debianlinux-6.1< linux 6.1.162-1 (bookworm)linux 6.1.162-1 (bookworm)
linuxlinux
linuxlinux>= af2d14b01c32d7cba65f73503586e5b621afb139 < be0974be5c42584e027883ac2af7dab5e950098cbe0974be5c42584e027883ac2af7dab5e950098c
linuxlinux>= af2d14b01c32d7cba65f73503586e5b621afb139 < 0a59a3895f804469276d188effa511c72e752f350a59a3895f804469276d188effa511c72e752f35
linuxlinux>= af2d14b01c32d7cba65f73503586e5b621afb139 < 88aab153d1528bc559292a12fb5105ee97528e1f88aab153d1528bc559292a12fb5105ee97528e1f
linuxlinux>= af2d14b01c32d7cba65f73503586e5b621afb139 < 6e5bff40bb38741e40c33043ba0816fba5f936616e5bff40bb38741e40c33043ba0816fba5f93661
linuxlinux>= af2d14b01c32d7cba65f73503586e5b621afb139 < 7b240a8935d554ad36a52c2c37c32039f9afaef27b240a8935d554ad36a52c2c37c32039f9afaef2
linuxlinux>= af2d14b01c32d7cba65f73503586e5b621afb139 < a21704df4024708be698fb3fd5830d5b113b70e0a21704df4024708be698fb3fd5830d5b113b70e0
linuxlinux>= af2d14b01c32d7cba65f73503586e5b621afb139 < 193d18f60588e95d62e0f82b6a53893e5f2f19f8193d18f60588e95d62e0f82b6a53893e5f2f19f8
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.249-15.10.249-1
linuxlinux_kernel>= 0 < 6.1.162-16.1.162-1
linuxlinux_kernel>= 0 < 6.12.69-16.12.69-1
linuxlinux_kernel>= 0 < 6.18.5-16.18.5-1
linuxlinux_kernel>= 0 < 5.15.0-173.1835.15.0-173.183
linuxlinux_kernel>= 5.11 < 5.15.1985.15.198

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.8HIGH
vendor_ubuntu7.8HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.