dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53098

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.6.141 / 6.12.91 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Use-after-free vulnerability in mt7915 wifi driver where crash_data is freed during device removal but dump_work workqueue item may still be executing, leading to dereferencing freed memory. The race condition occurs between device removal and pending work execution.

MitigationApply the kernel patch adding cancel_work_sync() in mt7915_unregister_device() to ensure pending/executing dump work completes before crash_data deallocation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against vulnerable ranges
    Run `uname -r` to get the kernel version, then compare it to the affected ranges: >= 6.2, < 6.6.141; >= 6.7, < 6.12.91; >= 6.13, < 6.18.33; >= 6.19, < 7.0.10
    Affected if The running kernel version falls within any of these ranges
  2. Determine if mt7915 WiFi driver is present
    Run `lsmod | grep mt7915` or check for the driver file existence at `/sys/module/mt7915*`
    Affected if The mt7915 kernel module is loaded or present in the system
  3. Check if MediaTek WiFi hardware using mt7915 is present
    Run `lspci | grep -i mediatek` or `ip link show` to list wireless interfaces, then check if any interface corresponds to mt7915 hardware
    Affected if A network interface backed by the mt7915 chipset is present and active
  4. Verify coredump support is enabled for the driver
    Check kernel config for CONFIG_MT7915_DEBUG or CONFIG_MT7915_COREDUMP, or inspect if /sys/kernel/debug/mt7915/ or similar debug paths exist when the driver is loaded
    Affected if The coredump functionality of the mt7915 driver is compiled in and available, as the vulnerability involves crash_data used in coredump handling

The system is affected if it runs a vulnerable kernel version AND has the mt7915 WiFi driver loaded with mt7915 hardware present, enabling the race condition between workqueue execution and crash_data deallocation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.6.141 / 6.12.91 / 6.18.33 or later
Fixed in 6.6.1416.12.916.18.33
Interim mitigation

Apply the kernel patch adding cancel_work_sync() in mt7915_unregister_device() to ensure pending/executing dump work completes before crash_data deallocation.

Recommended fix High confidence

Linux kernel 6.6.141, 6.12.91, 6.18.33, or 7.0.10 (depending on which version branch you are on)

  1. 1. Identify the currently running Linux kernel version using `uname -r`
  2. 2. Determine which version range your current kernel falls into from the affected versions: >= 6.2,<6.6.141; >=6.7,<6.12.91; >=6.13,<6.18.33; or >=6.19,<7.0.10
  3. 3. Upgrade the Linux kernel to the fixed release for your version branch: 6.6.141, 6.12.91, 6.18.33, or 7.0.10 respectively
  4. 4. For distribution-based systems, apply vendor-supplied kernel updates via package manager (e.g., `apt update && apt upgrade`, `yum update`, or `dnf update`)
  5. 5. Reboot the system to load the patched kernel
  6. 6. Verify the fix is applied by checking `uname -r` shows a version at or above the fixed release for your branch
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with third-party kernel modules or proprietary drivers

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53098 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53098 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data