CVE-2026-68307

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

wifi: mt76: mt7925: fix crash in reset link replay

During reset recovery, mt7925_vif_connect_iter() replays firmware state for links tracked in mvif->valid_links. After MLO link changes or MCU timeout recovery, the driver bitmap can temporarily contain a link whose mac80211 bss_conf has already gone away.

This can pass a NULL bss_conf to mt76_connac_mcu_uni_add_dev(), matching the crash where x1, the second argument, is NULL:

pc : mt76_connac_mcu_uni_add_dev+0x8c/0x1f8 [mt76_connac_lib] lr : mt7925_vif_connect_iter+0x9c/0x168 [mt7925_common] x2 : ffffff80a77f6018 x1 : 0000000000000000 x0 : ffffff8099402080 Call trace: mt76_connac_mcu_uni_add_dev+0x8c/0x1f8 [mt76_connac_lib] mt7925_vif_connect_iter+0x9c/0x168 [mt7925_common] mt7925_mac_reset_work+0x264/0x2f8 [mt7925_common]

Skip missing bss_conf entries before replaying the link. Non-MLO AP/STA reset replay is unchanged because the helper still returns &vif->bss_conf for the legacy link.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-68307(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.53.1.el10_22026-09-08redhat

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
linux-6.126.12.100-1~deb12u16.12.101-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)6.12.101-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)7.1.6-1

Data Freshness Timeline

(refreshed 9× in last 7d / 34× 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.

  1. 2026-09-19 08:24 UTCVendor advisory
  2. 2026-09-19 08:23 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 11:06 UTCVendor advisory
  6. 2026-09-16 11:06 UTCGHSA enrichment
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-13 11:55 UTCVendor advisory
  9. 2026-09-13 11:55 UTCGHSA enrichment
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 09:37 UTCEPSS rescore
  12. 2026-09-10 14:38 UTCVendor advisory
  13. 2026-09-10 14:38 UTCGHSA enrichment
  14. 2026-09-08 22:01 UTCEPSS rescore
  15. 2026-09-07 17:21 UTCGHSA enrichment
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-06 13:47 UTCEPSS rescore
  18. 2026-09-05 15:31 UTCEPSS rescore
  19. 2026-09-04 08:26 UTCGHSA enrichment
  20. 2026-09-04 05:07 UTCEPSS rescore
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 07:19 UTCGHSA enrichment
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 28 more
  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 10:02 UTCGHSA enrichment
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-25 21:49 UTCGHSA enrichment
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-23 00:11 UTCGHSA enrichment
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 22:56 UTCEPSS rescore
  10. 2026-08-20 02:54 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 05:37 UTCGHSA enrichment
  16. 2026-08-17 05:26 UTCNVD update
  17. 2026-08-17 05:06 UTCGHSA enrichment
  18. 2026-08-17 05:05 UTCMITRE cvelistV5
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 08:00 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 10:43 UTCEG score recompute
  24. 2026-08-13 10:43 UTCGHSA enrichment
  25. 2026-08-12 13:51 UTCEPSS rescore
  26. 2026-08-10 13:24 UTCNVD update
  27. 2026-08-10 12:19 UTCEG score recompute
  28. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68307?
CVE-2026-68307 is a publicly disclosed vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: fix crash in reset link replay During reset recovery, mt7925vifconnect_iter() replays firmware state for links tracked in mvif->valid_links. After MLO link changes or MCU timeout recovery, the driver bitmap can…
When was CVE-2026-68307 disclosed?
CVE-2026-68307 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68307 actively exploited?
CVE-2026-68307 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 93.5% of all scored CVEs.
How do I remediate CVE-2026-68307?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68307, 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-68307

Explore →

Is Your Infrastructure Affected by CVE-2026-68307?

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