← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-53097

Last refreshed2026-10-23

Status: UPDATED  |  Advisory ID: CVE-2026-53097

Key Details

CVECVE-2026-53097
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-21
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-416 (Use After Free)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-53097
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-53097
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.