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-53102wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req()

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() mt76_connac_mcu_alloc_sta_req() allocates an skb which is expected to be freed eventually by mt76_mcu_skb_send_msg(). However, currently if an intermediate function fails before sending, the allocated skb is leaked. Specifically, mt76_connac_mcu_sta_wed_update() and mt76_connac_mcu_sta_key_tlv() may fail, leading to an immediate memory leak in the error path. Fix this by explicitly freeing the skb in these error paths. Commit 7c0f63fe37a5 ("wifi: mt76: mt7996: fix memory leak on mt7996_mcu_sta_key_tlv error") made a similar change. Compile tested only. Issue found using a prototype static analysis tool and code review.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-53102, 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.12% · top 98% of all CVEs (13 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 6683d988089ce0e80bd859a9493333b6b272420e – < 25af8229133c8dc69b12721ad84165cced83caed
    • affected 6683d988089ce0e80bd859a9493333b6b272420e – < a2af91af9536922edc3f63de90c3f1fe9db71717
    • affected 6683d988089ce0e80bd859a9493333b6b272420e – < 7de35b99503012e57bec027e98ed53f881518b5b
    • affected 6683d988089ce0e80bd859a9493333b6b272420e – < 8527ac1bce87aaabde6755e8e6eb2a9f439d1292
    • affected 6683d988089ce0e80bd859a9493333b6b272420e – < eb466406d2094deefadc2cd6ddb4f6eeb086d1b4
    • affected 6683d988089ce0e80bd859a9493333b6b272420e – < c41075ce8cf05ed8c0e7b7efef000dce548ffc42
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 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-53102 badge
[![CVE-2026-53102](https://cveledger.app/badge/CVE-2026-53102.svg)](https://cveledger.app/cve/CVE-2026-53102)

Record last updated .