Skip to main content
VulnerabilityPublished Updated

CVE-2026-53097: Linux kernel · wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in c8f62f73bbced3a79894655bdb0b625462d956fc : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:30 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in c8f62f73bbced3a79894655bdb0b625462d956fc, aa4a31cd89f4fde5043ac613fe0e27014a60a60b, 180182a3f23ff79430a32ca2c4c1885368ceab48 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, < c8f62f73bbced3a79894655bdb0b625462d956fc
Fixed in
  • c8f62f73bbced3a79894655bdb0b625462d956fc
LinuxLinuxAffected
  • ≥ 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, < aa4a31cd89f4fde5043ac613fe0e27014a60a60b
Fixed in
  • aa4a31cd89f4fde5043ac613fe0e27014a60a60b
LinuxLinuxAffected
  • ≥ 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, < 180182a3f23ff79430a32ca2c4c1885368ceab48
Fixed in
  • 180182a3f23ff79430a32ca2c4c1885368ceab48
LinuxLinuxAffected
  • ≥ 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, < 533b1a9fa0128c75e40dd2d2c38a32b4e660741f
Fixed in
  • 533b1a9fa0128c75e40dd2d2c38a32b4e660741f
LinuxLinuxAffected
  • ≥ 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, < 188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6d
Fixed in
  • 188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6d
LinuxLinuxAffected
  • =6.4
Fixed in–

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.

References

Community reviews

Loading reviews…