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-53097wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work()

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work() When the mt7996 pci chip is detaching, the mt7996_crash_data is released in mt7996_coredump_unregister(). However, the work item dump_work may still be running or pending, leading to UAF bugs when the already freed crash_data is dereferenced again in mt7996_mac_dump_work(). The race condition can occur as follows: CPU 0 (removal path) | CPU 1 (workqueue) mt7996_pci_remove() | mt7996_sys_recovery_set() mt7996_unregister_device() | mt7996_reset() mt7996_coredump_unregister() | queue_work() vfree(dev->coredump.crash_data) | mt7996_mac_dump_work() | crash_data-> // UAF Fix this by ensuring dump_work is properly canceled before the crash_data is deallocated. Add cancel_work_sync() in mt7996_unregister_device() to synchronize with any pending or executing dump work.

Timeline

  1. ID reserved

    By Linux

  2. · 15 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-53097, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (19 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 – < 533b1a9fa0128c75e40dd2d2c38a32b4e660741f
    • affected 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 – < 180182a3f23ff79430a32ca2c4c1885368ceab48
    • affected 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 – < aa4a31cd89f4fde5043ac613fe0e27014a60a60b
    • affected 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 – < 188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6d
    • affected 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 – < c8f62f73bbced3a79894655bdb0b625462d956fc
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • 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

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .