Skip to main content

Linux Kernel CVE-2026-53098

| EUVDEUVD-2026-38966 HIGH
Use After Free (CWE-416)
2026-06-24 Linux GHSA-2w76-gx46-cq6p
7.8
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
4.7 MEDIUM

Local trigger and narrow removal-vs-workqueue race justify AV:L and AC:H; PR:L for inducing detach/recovery; impact is a kernel crash so A:H with C/I:N.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
6.4 MEDIUM
AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 21, 2026 - 20:38 vuln.today
CVSS changed
Jul 21, 2026 - 18:22 NVD
7.8 (HIGH)
Patch available
Jun 24, 2026 - 18:02 EUVD
CVE Published
Jun 24, 2026 - 16:30 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 24, 2026 - 16:30 nvd
HIGH 7.8

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work()

When the mt7915 pci chip is detaching, the mt7915_crash_data is released in mt7915_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 mt7915_mac_dump_work().

The race condition can occur as follows:

CPU 0 (removal path) | CPU 1 (workqueue) mt7915_pci_remove() | mt7915_sys_recovery_set() mt7915_unregister_device() | mt7915_reset() mt7915_coredump_unregister() | queue_work() vfree(dev->coredump.crash_data) | mt7915_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 mt7915_unregister_device() to synchronize with any pending or executing dump work.

AnalysisAI

Use-after-free in the Linux kernel's mt76/mt7915 MediaTek Wi-Fi driver allows local low-privileged users to corrupt kernel memory during PCI device detachment. When an mt7915 chip is removed, mt7915_coredump_unregister() frees the crash_data buffer while the dump_work item may still be pending or executing, causing mt7915_mac_dump_work() to dereference freed memory. Tagged as denial-of-service and memory corruption (CWE-416); there is no public exploit identified at time of analysis, EPSS is low (0.17%, 6th percentile), and it is not listed in CISA KEV.

Technical ContextAI

The affected component is the mt76 driver framework, specifically the mt7915 sub-driver that supports MediaTek MT7915-series 802.11ax (Wi-Fi 6) PCIe chipsets in the Linux kernel. The root cause is CWE-416 (Use-After-Free): a lifetime/synchronization gap between the device-removal path and a deferred workqueue item. During mt7915_pci_remove() -> mt7915_unregister_device() -> mt7915_coredump_unregister(), the crash_data buffer is released with vfree(), but the asynchronous dump_work (queued via mt7915_reset()/mt7915_sys_recovery_set() during firmware crash recovery) can still run mt7915_mac_dump_work() and dereference the now-freed dev->coredump.crash_data. The CPE data identifies the affected product generically as cpe:2.3:a:linux:linux, i.e. the mainline Linux kernel, with the driver code present in the wireless subsystem. The fix adds cancel_work_sync() in mt7915_unregister_device() to guarantee the work item completes or is cancelled before the buffer is deallocated.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 6.6.141, 6.12.91, 6.18.33, 7.0.10, or 7.1 or later, depending on your branch. The upstream fixes are the commits at https://git.kernel.org/stable/c/6d5202409467d621b6d1dfd7fc7dadb997fe66d2 and the sibling stable backports (e6856af8a22a, 6b7cbb13c838, 21ce6d867867, 1146d0946b53). On Ubuntu, apply the kernel updates in USN-8566-1, USN-8567-1, and USN-8568-1 (https://ubuntu.com/security/notices/USN-8566-1) and reboot. If immediate patching is not possible, the practical compensating control is to prevent the trigger condition: unload or blacklist the mt7915e driver (e.g., blacklist mt7915e in modprobe if the MediaTek Wi-Fi adapter is not needed), which eliminates the vulnerable code path at the cost of disabling that Wi-Fi interface; alternatively restrict local/physical access and avoid administrative operations that hot-remove the PCIe Wi-Fi device, since the race is tied to device detach during crash recovery.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-HPC-Azure Affected
Image SLES15-SP7-BYOS-Azure Image SLES15-SP7-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-Aliyun Image SLES15-SP7-CHOST-BYOS-Azure Image SLES15-SP7-CHOST-BYOS-EC2 Image SLES15-SP7-CHOST-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-GDC Image SLES15-SP7-CHOST-BYOS-SAP-CCloud Image SLES15-SP7-EC2 Image SLES15-SP7-EC2-ECS-HVM Image SLES15-SP7-GCE Image SLES15-SP7-HPC-BYOS-Azure Image SLES15-SP7-HPC-BYOS-EC2 Image SLES15-SP7-HPC-BYOS-GCE Image SLES15-SP7-Hardened-BYOS-Azure Image SLES15-SP7-Hardened-BYOS-EC2 Image SLES15-SP7-Hardened-BYOS-GCE Image SLES15-SP7-SAPCAL-Azure Image SLES15-SP7-SAPCAL-EC2 Image SLES15-SP7-SAPCAL-GCE Affected
Image SLES15-SP7-SAP-Azure Image SLES15-SP7-SAP-Azure-3P Image SLES15-SP7-SAP-BYOS-Azure Image SLES15-SP7-SAP-BYOS-EC2 Image SLES15-SP7-SAP-BYOS-GCE Image SLES15-SP7-SAP-EC2 Image SLES15-SP7-SAP-GCE Image SLES15-SP7-SAP-Hardened-Azure Image SLES15-SP7-SAP-Hardened-BYOS-Azure Image SLES15-SP7-SAP-Hardened-BYOS-EC2 Image SLES15-SP7-SAP-Hardened-BYOS-GCE Image SLES15-SP7-SAP-Hardened-GCE Affected
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed

Share

CVE-2026-53098 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy