CVE-2026-53100

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 deadlock in remain-on-channel

mt76_remain_on_channel() and mt76_roc_complete() call mt76_set_channel() while already holding dev->mutex. Since mt76_set_channel() also acquires dev->mutex, this results in a deadlock.

Use __mt76_set_channel() instead of mt76_set_channel(). Add cancel_delayed_work_sync() for mac_work before acquiring the mutex in mt76_remain_on_channel() to prevent a secondary deadlock with the mac_work workqueue.

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: fix deadlock in remain-on-channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a89c245d203aa0ed5ff2d68ac05b48b2ef9fa3f
generic

wifi: mt76: fix deadlock in remain-on-channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6939b97ddad3cf3dfbb3b5a0a12ef79cb886747e
generic

wifi: mt76: fix deadlock in remain-on-channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5fc8c5d45e44575dda9fcabdc2aac4ad97baf0cd

Vendor Advisories for CVE-2026-53100(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)

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

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

(1 across 1 ecosystem)
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)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 19× 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 147 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 15:14 UTCEG score recompute
  3. 2026-08-24 15:14 UTCVendor advisory
  4. 2026-08-24 15:14 UTCGHSA enrichment
  5. 2026-08-23 13:26 UTCEG score recompute
  6. 2026-08-23 13:26 UTCVendor advisory
  7. 2026-08-23 13:26 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 11:31 UTCEG score recompute
  10. 2026-08-22 11:31 UTCVendor advisory
  11. 2026-08-22 11:31 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 09:13 UTCEG score recompute
  14. 2026-08-21 09:13 UTCVendor advisory
  15. 2026-08-21 09:13 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 07:19 UTCEG score recompute
  18. 2026-08-20 07:19 UTCVendor advisory
  19. 2026-08-20 07:19 UTCGHSA enrichment
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 02:03 UTCEG score recompute
  22. 2026-08-19 02:03 UTCVendor advisory
  23. 2026-08-19 02:03 UTCGHSA enrichment
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 11:57 UTCEG score recompute
Show 75 more
  1. 2026-08-17 11:57 UTCVendor advisory
  2. 2026-08-17 11:57 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 10:18 UTCEG score recompute
  5. 2026-08-16 10:18 UTCVendor advisory
  6. 2026-08-16 10:18 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 08:39 UTCEG score recompute
  9. 2026-08-15 08:39 UTCVendor advisory
  10. 2026-08-15 08:39 UTCGHSA enrichment
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 06:36 UTCEG score recompute
  13. 2026-08-14 06:36 UTCVendor advisory
  14. 2026-08-14 06:36 UTCGHSA enrichment
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 04:56 UTCVendor advisory
  17. 2026-08-13 04:56 UTCGHSA enrichment
  18. 2026-08-12 03:17 UTCEG score recompute
  19. 2026-08-12 03:17 UTCVendor advisory
  20. 2026-08-12 03:17 UTCGHSA enrichment
  21. 2026-08-11 01:38 UTCVendor advisory
  22. 2026-08-11 01:38 UTCGHSA enrichment
  23. 2026-08-09 23:59 UTCEG score recompute
  24. 2026-08-09 23:59 UTCVendor advisory
  25. 2026-08-09 23:59 UTCGHSA enrichment
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-08 22:20 UTCEG score recompute
  28. 2026-08-08 22:20 UTCVendor advisory
  29. 2026-08-08 22:20 UTCGHSA enrichment
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-07 20:39 UTCEG score recompute
  32. 2026-08-07 20:39 UTCVendor advisory
  33. 2026-08-07 20:39 UTCGHSA enrichment
  34. 2026-08-06 19:00 UTCEG score recompute
  35. 2026-08-06 19:00 UTCVendor advisory
  36. 2026-08-06 19:00 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-05 17:21 UTCEG score recompute
  40. 2026-08-05 17:21 UTCVendor advisory
  41. 2026-08-05 17:20 UTCGHSA enrichment
  42. 2026-08-04 15:10 UTCEPSS rescore
  43. 2026-08-04 15:10 UTCEG score recompute
  44. 2026-08-04 15:10 UTCVendor advisory
  45. 2026-08-04 15:10 UTCGHSA enrichment
  46. 2026-08-03 10:36 UTCEPSS rescore
  47. 2026-08-03 09:32 UTCVendor advisory
  48. 2026-08-03 09:32 UTCGHSA enrichment
  49. 2026-08-02 07:47 UTCVendor advisory
  50. 2026-08-02 07:47 UTCGHSA enrichment
  51. 2026-08-01 06:08 UTCEG score recompute
  52. 2026-08-01 06:08 UTCVendor advisory
  53. 2026-08-01 06:07 UTCGHSA enrichment
  54. 2026-08-01 04:16 UTCEPSS rescore
  55. 2026-07-31 04:11 UTCEG score recompute
  56. 2026-07-31 04:11 UTCVendor advisory
  57. 2026-07-31 04:11 UTCGHSA enrichment
  58. 2026-07-30 16:28 UTCEPSS rescore
  59. 2026-07-30 02:30 UTCEG score recompute
  60. 2026-07-30 02:30 UTCGHSA enrichment
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-29 00:49 UTCEG score recompute
  63. 2026-07-29 00:49 UTCGHSA enrichment
  64. 2026-07-28 15:37 UTCEPSS rescore
  65. 2026-07-27 17:36 UTCEG score recompute
  66. 2026-07-27 17:36 UTCGHSA enrichment
  67. 2026-07-26 15:28 UTCEG score recompute
  68. 2026-07-26 15:28 UTCVendor advisory
  69. 2026-07-26 15:28 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-53100?
CVE-2026-53100 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: fix deadlock in remain-on-channel mt76remainonchannel() and mt76roccomplete() call mt76set_channel() while already holding dev->mutex. Since mt76setchannel() also acquires dev->mutex, this results in a deadlock. Use…
When was CVE-2026-53100 disclosed?
CVE-2026-53100 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-53100 actively exploited?
CVE-2026-53100 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-53100?
CVE-2026-53100 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53100?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53100, 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-53100

Explore →

Is Your Infrastructure Affected by CVE-2026-53100?

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

Start Free Scan →Browse All CVEs