Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-71127wifi: mac80211: Discard Beacon frames to non-broadcast address

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-71127, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected af2d14b01c32d7cba65f73503586e5b621afb139 – < be0974be5c42584e027883ac2af7dab5e950098c
    • affected af2d14b01c32d7cba65f73503586e5b621afb139 – < 0a59a3895f804469276d188effa511c72e752f35
    • affected af2d14b01c32d7cba65f73503586e5b621afb139 – < 88aab153d1528bc559292a12fb5105ee97528e1f
    • affected af2d14b01c32d7cba65f73503586e5b621afb139 – < 6e5bff40bb38741e40c33043ba0816fba5f93661
    • affected af2d14b01c32d7cba65f73503586e5b621afb139 – < 7b240a8935d554ad36a52c2c37c32039f9afaef2
    • affected af2d14b01c32d7cba65f73503586e5b621afb139 – < a21704df4024708be698fb3fd5830d5b113b70e0
    • affected af2d14b01c32d7cba65f73503586e5b621afb139 – < 193d18f60588e95d62e0f82b6a53893e5f2f19f8
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.65 – ≤ 6.12.*
    • unaffected 6.18.4 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-71127 badge
[![CVE-2025-71127](https://cveledger.app/badge/CVE-2025-71127.svg)](https://cveledger.app/cve/CVE-2025-71127)

Record last updated .