CVE-2026-53097: wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 180182a3f23ff79430a32ca2c4c1885368ceab48, 188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6d, 533b1a9fa0128c75e40dd2d2c38a32b4e660741f.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 180182a3f23ff79430a32ca2c4c1885368ceab48, 188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6d, 533b1a9fa0128c75e40dd2d2c38a32b4e660741f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 24, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.4affected
- 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 and later · before 533b1a9fa0128c75e40dd2d2c38a32b4e660741faffected · git
- 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 and later · before 180182a3f23ff79430a32ca2c4c1885368ceab48affected · git
- 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 and later · before aa4a31cd89f4fde5043ac613fe0e27014a60a60baffected · git
- 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 and later · before 188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6daffected · git
- 878161d5d4a469a6ef7f3fb4fe9f676bc508ee99 and later · before c8f62f73bbced3a79894655bdb0b625462d956fcaffected · git
- before 6.4not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.91 and later · up to and including 6.12.*not affected · semver
- 6.18.33 and later · up to and including 6.18.*not affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.4 and later · before 6.12.91
- linux linux kernel6.13 and later · before 6.18.33
- linux linux kernel6.19 and later · before 7.0.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.10-1 | 7.0.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53094Jun 24, 2026 · bpf: Fix stale offload->prog pointer after constant blinding31Monitor
- ← EarlierCVE-2026-53096Jun 24, 2026 · bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path31Monitor
- Later →CVE-2026-53100Jun 24, 2026 · wifi: mt76: fix deadlock in remain-on-channel22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 180182a3f23ff79430a32ca2c4c1885368ceab48 | Vendor (CNA) |
| Linux Linux | 188e10f9ea3109d23c6b7643aa6ec2f5cb0faa6d | Vendor (CNA) |
| Linux Linux | 533b1a9fa0128c75e40dd2d2c38a32b4e660741f | Vendor (CNA) |
| Linux Linux | aa4a31cd89f4fde5043ac613fe0e27014a60a60b | Vendor (CNA) |
| Linux Linux | c8f62f73bbced3a79894655bdb0b625462d956fc | Vendor (CNA) |
| debian:linux | 6.12.94-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0440 · Jun 25, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.