dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53105

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.12.91 / 6.18.33 or later.
See remediation →
57/100
Remediation priority · Elevated
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: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi Check for a NULL `vif` before accessing `ieee80211_vif_is_mld(vif)` to avoid a potential kernel panic in scenarios where `vif` might not be initialized.

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 · moderate confidence

A NULL pointer dereference vulnerability exists in the mt7925 WiFi driver where the code accesses ieee80211_vif_is_mld(vif) without first checking if vif is NULL, potentially causing a kernel panic when the virtual interface is not initialized.

MitigationApply the kernel patch that adds a NULL check for vif before calling ieee80211_vif_is_mld(vif) in the mt7925_mac_write_txwi function to prevent the NULL dereference.

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.11, < 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 your kernel version
    Run 'uname -r' or 'cat /proc/version' to get the running kernel version
    Affected if The version falls within >= 6.11, < 6.12.91; >= 6.13, < 6.18.33; or >= 6.19, < 7.0.10
  2. Verify the mt7925 driver is present
    Run 'lsmod | grep mt7925' or check /lib/modules/$(uname -r)/kernel/drivers/net/wireless/mediatek/mt76/ for mt7925 files
    Affected if The mt7925 driver module or files exist on the system
  3. Identify active wireless interfaces using mt7925
    Run 'ip link show' to list interfaces, then 'ethtool -i <interface>' or check 'iw dev' output to see which driver each wireless interface uses
    Affected if Any wireless interface is using the mt7925 driver
  4. Check for kernel panics or NULL dereference errors in logs
    Run 'dmesg | grep -i panic' or 'journalctl -k | grep -i null' and look for errors referencing 'mt7925_mac_write_txwi' or 'ieee80211_vif_is_mld'
    Affected if Kernel crash logs show NULL pointer dereference related to the mt7925 driver and vif handling

You are affected if your kernel version is in the vulnerable range AND the mt7925 wireless driver is loaded and actively managing a wireless interface, or if crash logs show the specific NULL dereference in mt7925_mac_write_txwi.

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.12.91 / 6.18.33 / 7.0.10 or later
Fixed in 6.12.916.18.337.0.10
Interim mitigation

Apply the kernel patch that adds a NULL check for vif before calling ieee80211_vif_is_mld(vif) in the mt7925_mac_write_txwi function to prevent the NULL dereference.

Recommended fix High confidence

Linux Kernel 6.18.33 (LTS) or 7.0.10+ for mainline

  1. Identify your current Linux kernel version using `uname -r`
  2. Determine which kernel branch you are running (6.11-6.12.x, 6.13-6.18.x, or 6.19.x)
  3. For 6.11-6.12.x branch: Upgrade to kernel version 6.12.91 or later
  4. For 6.13-6.18.x branch: Upgrade to kernel version 6.18.33 or later
  5. For 6.19.x branch: Upgrade to kernel version 7.0.10 or later
  6. Reboot the system to load the new kernel
  7. Verify the fix is applied by checking the mt7925 driver loads without errors
Caveat Minimal risk - this is a defensive NULL check addition to prevent kernel panic; no functional changes to driver behavior

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53105 — 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-53105 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