CVE-2025-68360

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. A secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2025-205094 (ENISA EUVD) · GHSA-9j3g-9p96-vfm4 (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks

MT7996 driver can use both wed and wed_hif2 devices to offload traffic from/to the wireless NIC. In the current codebase we assume to always use the primary wed device in wed callbacks resulting in the following crash if the hw runs wed_hif2 (e.g. 6GHz link).

[ 297.455876] Unable to handle kernel read from unreadable memory at virtual address 000000000000080a [ 297.464928] Mem abort info: [ 297.467722] ESR = 0x0000000096000005 [ 297.471461] EC = 0x25: DABT (current EL), IL = 32 bits [ 297.476766] SET = 0, FnV = 0 [ 297.479809] EA = 0, S1PTW = 0 [ 297.482940] FSC = 0x05: level 1 translation fault [ 297.487809] Data abort info: [ 297.490679] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 297.496156] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 297.501196] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 297.506500] user pgtable: 4k pages, 39-bit VAs, pgdp=0000000107480000 [ 297.512927] [000000000000080a] pgd=08000001097fb003, p4d=08000001097fb003, pud=08000001097fb003, pmd=0000000000000000 [ 297.523532] Internal error: Oops: 0000000096000005 [#1] SMP [ 297.715393] CPU: 2 UID: 0 PID: 45 Comm: kworker/u16:2 Tainted: G O 6.12.50 #0 [ 297.723908] Tainted: [O]=OOT_MODULE [ 297.727384] Hardware name: Banana Pi BPI-R4 (2x SFP+) (DT) [ 297.732857] Workqueue: nf_ft_offload_del nf_flow_rule_route_ipv6 [nf_flow_table] [ 297.740254] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 297.747205] pc : mt76_wed_offload_disable+0x64/0xa0 [mt76] [ 297.752688] lr : mtk_wed_flow_remove+0x58/0x80 [ 297.757126] sp : ffffffc080fe3ae0 [ 297.760430] x29: ffffffc080fe3ae0 x28: ffffffc080fe3be0 x27: 00000000deadbef7 [ 297.767557] x26: ffffff80c5ebca00 x25: 0000000000000001 x24: ffffff80c85f4c00 [ 297.774683] x23: ffffff80c1875b78 x22: ffffffc080d42cd0 x21: ffffffc080660018 [ 297.781809] x20: ffffff80c6a076d0 x19: ffffff80c6a043c8 x18: 0000000000000000 [ 297.788935] x17: 0000000000000000 x16: 0000000000000001 x15: 0000000000000000 [ 297.796060] x14: 0000000000000019 x13: ffffff80c0ad8ec0 x12: 00000000fa83b2da [ 297.803185] x11: ffffff80c02700c0 x10: ffffff80c0ad8ec0 x9 : ffffff81fef96200 [ 297.810311] x8 : ffffff80c02700c0 x7 : ffffff80c02700d0 x6 : 0000000000000002 [ 297.817435] x5 : 0000000000000400 x4 : 0000000000000000 x3 : 0000000000000000 [ 297.824561] x2 : 0000000000000001 x1 : 0000000000000800 x0 : ffffff80c6a063c8 [ 297.831686] Call trace: [ 297.834123] mt76_wed_offload_disable+0x64/0xa0 [mt76] [ 297.839254] mtk_wed_flow_remove+0x58/0x80 [ 297.843342] mtk_flow_offload_cmd+0x434/0x574 [ 297.847689] mtk_wed_setup_tc_block_cb+0x30/0x40 [ 297.852295] nf_flow_offload_ipv6_hook+0x7f4/0x964 [nf_flow_table] [ 297.858466] nf_flow_rule_route_ipv6+0x438/0x4a4 [nf_flow_table] [ 297.864463] process_one_work+0x174/0x300 [ 297.868465] worker_thread+0x278/0x430 [ 297.872204] kthread+0xd8/0xdc [ 297.875251] ret_from_fork+0x10/0x20 [ 297.878820] Code: 928b5ae0 8b000273 91400a60 f943fa61 (79401421) [ 297.884901] ---[ end trace 0000000000000000 ]---

Fix the issue detecting the proper wed reference to use running wed callabacks.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 24, 2025

Last Modified

October 21, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
Patch available.
Web page

wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d582d0e988d696698c94edf097062bb987ae592c
Web page

wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ab94ecb997fd1bbc501a0116c7aad51556b67c86
Web page

wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/385aab8fccd7a8746b9f1a17f3c1e38498a14bc7

Vendor Advisories for CVE-2025-68360(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1010.10) @ questing2026-10-28ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9) @ questing2026-10-28ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-10-28ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-10-28ubuntu
linuxKernel @ 6.17.13 (fixes >=6.8.0)—osv

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 rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.9-1 (85 versions)
  • every version up to 6.17.13-1: fixed in 6.17.13-1
—

All Vendor Advisories

(7)

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 10× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 254 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 155 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-68360?
CVE-2025-68360 is a high-severity vulnerability; its CVE record was published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks MT7996 driver can use both wed and wed_hif2 devices to offload traffic from/to the wireless NIC. In the current codebase we assume to always use the primary…
When was the CVE record for CVE-2025-68360 published?
The CVE record for CVE-2025-68360 was published on December 24, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 21, 2026; the record at its source may have been updated since.
Is CVE-2025-68360 actively exploited?
CVE-2025-68360 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68360?
CVE-2025-68360 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-68360?
A fix for CVE-2025-68360 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-68360 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68360

Explore →

Is Your Infrastructure Affected by CVE-2025-68360?

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

Book a Demo →Browse All CVEs