CVE-2026-53103

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: mt7925: fix potential deadlock in mt7925_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() -> mt7925_mac_sta_remove_link() -> mt7925_mac_link_sta_remove() -> mt7925_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 (3)

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

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

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

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

https://git.kernel.org/stable/c/2d8e0053bca29143ace51e08c980ff076844a4b0
generic

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

https://git.kernel.org/stable/c/153bcba36c87a1ba555b57b6c49028d5812f895b

Vendor Advisories for CVE-2026-53103(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.100-1 ... 7.2~rc5-1~exp1 (160 versions)
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 19× in last 7d / 79× 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 136 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53103?
CVE-2026-53103 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: fix potential deadlock in mt7925rocabort_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-53103 disclosed?
CVE-2026-53103 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-53103 actively exploited?
CVE-2026-53103 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-53103?
CVE-2026-53103 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53103, 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-53103

Explore →

Is Your Infrastructure Affected by CVE-2026-53103?

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