dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53102

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 7.0.10 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: Fix memory leak after mt76_connac_mcu_alloc_sta_req() mt76_connac_mcu_alloc_sta_req() allocates an skb which is expected to be freed eventually by mt76_mcu_skb_send_msg(). However, currently if an intermediate function fails before sending, the allocated skb is leaked. Specifically, mt76_connac_mcu_sta_wed_update() and mt76_connac_mcu_sta_key_tlv() may fail, leading to an immediate memory leak in the error path. Fix this by explicitly freeing the skb in these error paths. Commit 7c0f63fe37a5 ("wifi: mt76: mt7996: fix memory leak on mt7996_mcu_sta_key_tlv error") made a similar change. Compile tested only. Issue found using a prototype static analysis tool and code review.

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

Memory leak in Linux kernel mt76 wifi driver where mt76_connac_mcu_alloc_sta_req() allocates an skb that should be freed by mt76_mcu_skb_send_msg(), but if mt76_connac_mcu_sta_wed_update() or mt76_connac_mcu_sta_key_tlv() fail before sending, the skb is leaked in the error path.

MitigationApply the kernel patch that adds explicit skb kfree_skb() calls in the error paths of mt76_connac_mcu_sta_wed_update() and mt76_connac_mcu_sta_key_tlv() functions, then rebuild and deploy the updated kernel module.

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:>= 5.18, < 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 kernel version
    Run 'uname -r' or 'cat /proc/version' to get the kernel version
    Affected if Kernel version is >= 5.18 and < 7.0.10 (for example, 5.18.x, 6.x.x, or 7.0.0-7.0.9)
  2. Identify mt76 driver usage
    Run 'lsmod | grep mt76' to check if any mt76 modules are loaded, or check kernel config with 'cat /boot/config-$(uname -r) | grep CONFIG_MT76'
    Affected if Any mt76 driver modules are loaded (such as mt76x2e, mt7615e, mt7921e) or CONFIG_MT76 is set in kernel config
  3. Verify wireless interfaces using mt76
    Run 'ip link show' and check for wireless interfaces, then run 'ethtool -i <interface>' or check 'iw dev' output to identify the driver
    Affected if Wireless interfaces are present and using mt76 driver (check driver name in ethtool output)
  4. Check for patched function symbols
    If available, use 'nm /lib/modules/$(uname -r)/kernel/drivers/net/wireless/mediatek/mt76/mt76x2e.ko | grep mt76_connac_mcu_sta_wed_update' or search vmlinux for these symbols
    Affected if Symbols mt76_connac_mcu_sta_wed_update or mt76_connac_mcu_sta_key_tlv exist in the mt76 driver binary and error handling code for skb freeing is missing

System is affected if kernel version is 5.18 or higher but below 7.0.10 AND the mt76 WiFi driver is in use (loaded module or built-in kernel).

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 7.0.10 or later
Fixed in 7.0.10
Interim mitigation

Apply the kernel patch that adds explicit skb kfree_skb() calls in the error paths of mt76_connac_mcu_sta_wed_update() and mt76_connac_mcu_sta_key_tlv() functions, then rebuild and deploy the updated kernel module.

Recommended fix High confidence

Linux Kernel 7.0.10

  1. Upgrade the Linux kernel to version 7.0.10 or later to receive the memory leak fix in the mt76 driver
  2. Alternatively, apply the upstream kernel patch that adds explicit skb freeing in the error paths of mt76_connac_mcu_sta_wed_update() and mt76_connac_mcu_sta_key_tlv() functions
  3. Verify the fix is applied by checking that the skb is properly freed in all error paths before mt76_mcu_skb_send_msg() is called

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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