boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Wednesday, August 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2025-71127MEDIUM
Linux Linux — wifi: mac80211: Discard Beacon frames to non-broadcast address
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   L   L   L   N  U  N  N  H    5.5   .0021   11.5     —
AFFECTED
  Product  Versions                                    Fixed
  Linux    af2d14b01c32d7cba65f73503586e5b621afb139 –  —
  Linux    5.7 –                                       5.10.248
TIMELINE
  Jan 13  Reserved by Linux
  Jan 14  Published (CNA: Linux)
  Jul 30  RESCORED — CVE-2025-71127 (Linux). CVSS 7.1 → 5.5 (NVD).
CNA: Linux · CVSS v3.1 · 7 references · NVD status: Modified

Description

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.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
January 13, 2026ReservedReserved by Linux
January 14, 2026PublishedPublished (CNA: Linux)
July 30, 2026RESCOREDRESCORED — CVE-2025-71127 (Linux). CVSS 7.1 → 5.5 (NVD).

Affected

Affected products and packages — 2 rows
VendorProduct / PackageEcosystemVersion introducedFixed
LinuxLinuxaf2d14b01c32d7cba65f73503586e5b621afb139
LinuxLinux5.75.10.248

References (7)

Related

Authoritative record: CVE-2025-71127 at cve.org

Vendors: linux

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2025-71127 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Wednesday, August 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.