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-2026-53317wifi: mt76: mt7921: Place upper limit on station AID

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921: Place upper limit on station AID Any station configured with an AID over 20 causes a firmware crash. This situation occurred in our testing using an AP interface on 7922 hardware, with a modified hostapd, sourced from Mediatek's OpenWRT feeds. In stock hostapd, station AIDs begin counting at 1, and this configuration is prevented with an upper limit on associated stations. However, the modified hostapd began allocation at 65, which caused the firmware to crash. This fix does not allow these AIDs to work, but will prevent the firmware crash. This crash was only seen on IFTYPE_AP interfaces, and the fix does not appear to have an effect on IFTYPE_STATION behavior.

Timeline

  1. ID reserved

    By Linux

  2. · 17 days later

    Published

  3. · 4 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-2026-53317, by who scored it
Scored byCVSSScoreVector
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.16% · top 95% of all CVEs (15 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 5c14a5f944b91371961548b1907802f74a4d2e5c – < 8f2ce0910b25173049910ec9a49304150534afd4
    • affected 5c14a5f944b91371961548b1907802f74a4d2e5c – < 9d63dd026644fa612a1fd348d5d3ab5d73df7fb8
    • affected 5c14a5f944b91371961548b1907802f74a4d2e5c – < 6dbe70f9ef14d8ac1c24bf19fd9510978a3ab952
    • affected 5c14a5f944b91371961548b1907802f74a4d2e5c – < 35835ff71e6e618155578b8e3905597edd5f601c
    • affected 5c14a5f944b91371961548b1907802f74a4d2e5c – < 1a4b802afe15c5b33b2dcb37a594aba2fa215d52
    • affected 5c14a5f944b91371961548b1907802f74a4d2e5c – < 4d0bf21e3e20619d51d06c0c36207aabab8b712c
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .