CVE-2026-53101

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: mt7921: fix potential deadlock in mt7921_roc_abort_sync

roc_abort_sync() can deadlock with roc_work(). roc_work() holds dev->mt76.mutex, while cancel_work_sync() waits for roc_work() to finish. If the caller already owns the same mutex, both sides block and no progress is possible.

This deadlock can occur during station removal when mt76_sta_state() -> mt76_sta_remove() -> mt7921_mac_sta_remove() -> mt7921_roc_abort_sync() invokes cancel_work_sync() while roc_work() is still running and holding dev->mt76.mutex.

This avoids the mutex deadlock and preserves exactly-once work ownership.

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

July 21, 2026

Advisory Details (4)

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

wifi: mt76: mt7921: fix potential deadlock in mt7921_roc_abort_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: mt76: mt7921: fix potential deadlock in mt7921_roc_abort_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: mt76: mt7921: fix potential deadlock in mt7921_roc_abort_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91e77840bf13de3add125060cf8b32ca24a52c8c
generic

wifi: mt76: mt7921: fix potential deadlock in mt7921_roc_abort_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35180c772f5e11e2fa4d80d3dfd50906cb6d9646

Vendor Advisories for CVE-2026-53101(1)

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

Patch Availability(8)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1

Weakness Classification(1)

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

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 18× in last 7d / 89× 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 148 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53101?
CVE-2026-53101 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921: fix potential deadlock in mt7921rocabort_sync rocabortsync() can deadlock with rocwork(). rocwork() holds dev->mt76.mutex, while cancelworksync() waits for roc_work() to finish. If the caller already owns the…
When was CVE-2026-53101 disclosed?
CVE-2026-53101 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53101 actively exploited?
CVE-2026-53101 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53101?
CVE-2026-53101 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53101?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53101, 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-53101

Explore →

Is Your Infrastructure Affected by CVE-2026-53101?

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