CVE-2026-53102

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

September 7, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eb466406d2094deefadc2cd6ddb4f6eeb086d1b4
generic

wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c41075ce8cf05ed8c0e7b7efef000dce548ffc42

Vendor Advisories for CVE-2026-53102(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-18ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 191 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 07:51 UTCEG score recompute
  4. 2026-09-18 07:51 UTCVendor advisory
  5. 2026-09-18 07:50 UTCGHSA enrichment
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-14 01:37 UTCEG score recompute
  9. 2026-09-14 01:37 UTCVendor advisory
  10. 2026-09-14 01:37 UTCGHSA enrichment
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-12 16:11 UTCEG score recompute
  13. 2026-09-12 16:11 UTCVendor advisory
  14. 2026-09-12 16:11 UTCGHSA enrichment
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 16:23 UTCEG score recompute
  19. 2026-09-07 16:23 UTCVendor advisory
  20. 2026-09-07 16:23 UTCGHSA enrichment
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-07 15:52 UTCEG score recompute
  23. 2026-09-07 15:52 UTCVendor advisory
  24. 2026-09-07 15:52 UTCGHSA enrichment
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 19:53 UTCEG score recompute
  6. 2026-08-30 19:53 UTCVendor advisory
  7. 2026-08-30 19:53 UTCGHSA enrichment
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-28 21:41 UTCEPSS rescore
  11. 2026-08-28 03:42 UTCEG score recompute
  12. 2026-08-28 03:42 UTCVendor advisory
  13. 2026-08-28 03:42 UTCGHSA enrichment
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-24 13:21 UTCEG score recompute
  18. 2026-08-24 13:21 UTCVendor advisory
  19. 2026-08-24 13:21 UTCGHSA enrichment
  20. 2026-08-23 12:00 UTCEG score recompute
  21. 2026-08-23 12:00 UTCVendor advisory
  22. 2026-08-23 12:00 UTCGHSA enrichment
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 11:31 UTCEG score recompute
  25. 2026-08-22 11:31 UTCVendor advisory
  26. 2026-08-22 11:31 UTCGHSA enrichment
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-21 07:48 UTCEG score recompute
  29. 2026-08-21 07:48 UTCVendor advisory
  30. 2026-08-21 07:48 UTCGHSA enrichment
  31. 2026-08-20 22:55 UTCEPSS rescore
  32. 2026-08-20 07:19 UTCEG score recompute
  33. 2026-08-20 07:19 UTCVendor advisory
  34. 2026-08-20 07:19 UTCGHSA enrichment
  35. 2026-08-19 17:04 UTCEPSS rescore
  36. 2026-08-19 02:03 UTCEG score recompute
  37. 2026-08-19 02:03 UTCVendor advisory
  38. 2026-08-19 02:03 UTCGHSA enrichment
  39. 2026-08-18 13:48 UTCEPSS rescore
  40. 2026-08-17 14:25 UTCEG score recompute
  41. 2026-08-17 14:25 UTCVendor advisory
  42. 2026-08-17 14:25 UTCGHSA enrichment
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 13:54 UTCEG score recompute
  45. 2026-08-16 13:54 UTCVendor advisory
  46. 2026-08-16 13:54 UTCGHSA enrichment
  47. 2026-08-16 02:14 UTCEPSS rescore
  48. 2026-08-15 13:25 UTCEG score recompute
  49. 2026-08-15 13:25 UTCVendor advisory
  50. 2026-08-15 13:25 UTCGHSA enrichment
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-14 12:55 UTCEG score recompute
  53. 2026-08-14 12:55 UTCVendor advisory
  54. 2026-08-14 12:55 UTCGHSA enrichment
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-13 12:26 UTCEG score recompute
  57. 2026-08-13 12:26 UTCVendor advisory
  58. 2026-08-13 12:26 UTCGHSA enrichment
  59. 2026-08-12 13:51 UTCEPSS rescore
  60. 2026-08-12 11:57 UTCEG score recompute
  61. 2026-08-12 11:57 UTCVendor advisory
  62. 2026-08-12 11:57 UTCGHSA enrichment
  63. 2026-08-11 11:28 UTCEG score recompute
  64. 2026-08-11 11:28 UTCVendor advisory
  65. 2026-08-11 11:28 UTCGHSA enrichment
  66. 2026-08-11 00:00 UTCEPSS rescore
  67. 2026-08-10 11:00 UTCEG score recompute
  68. 2026-08-10 11:00 UTCVendor advisory
  69. 2026-08-10 11:00 UTCGHSA enrichment
  70. 2026-08-09 13:46 UTCEPSS rescore
  71. 2026-08-09 10:30 UTCEG score recompute
  72. 2026-08-09 10:30 UTCVendor advisory
  73. 2026-08-09 10:30 UTCGHSA enrichment
  74. 2026-08-08 16:37 UTCEPSS rescore
  75. 2026-08-08 10:01 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53102?
CVE-2026-53102 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: Fix memory leak after mt76connacmcuallocsta_req() mt76connacmcuallocsta_req() allocates an skb which is expected to be freed eventually by mt76mcuskbsendmsg(). However, currently if an intermediate function fails before…
When was CVE-2026-53102 disclosed?
CVE-2026-53102 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on September 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53102 actively exploited?
CVE-2026-53102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53102?
CVE-2026-53102 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53102, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53102

Explore →

Is Your Infrastructure Affected by CVE-2026-53102?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs