CVE-2025-40000

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-15. A secondary CVSS source baseline 8.8; 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-34573 (ENISA EUVD) · GHSA-hp7r-72h5-wvvm (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait()

There is a bug observed when rtw89_core_tx_kick_off_and_wait() tries to access already freed skb_data:

BUG: KFENCE: use-after-free write in rtw89_core_tx_kick_off_and_wait drivers/net/wireless/realtek/rtw89/core.c:1110

CPU: 6 UID: 0 PID: 41377 Comm: kworker/u64:24 Not tainted 6.17.0-rc1+ #1 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS edk2-20250523-14.fc42 05/23/2025 Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]

Use-after-free write at 0x0000000020309d9d (in kfence-#251): rtw89_core_tx_kick_off_and_wait drivers/net/wireless/realtek/rtw89/core.c:1110 rtw89_core_scan_complete drivers/net/wireless/realtek/rtw89/core.c:5338 rtw89_hw_scan_complete_cb drivers/net/wireless/realtek/rtw89/fw.c:7979 rtw89_chanctx_proceed_cb drivers/net/wireless/realtek/rtw89/chan.c:3165 rtw89_chanctx_proceed drivers/net/wireless/realtek/rtw89/chan.h:141 rtw89_hw_scan_complete drivers/net/wireless/realtek/rtw89/fw.c:8012 rtw89_mac_c2h_scanofld_rsp drivers/net/wireless/realtek/rtw89/mac.c:5059 rtw89_fw_c2h_work drivers/net/wireless/realtek/rtw89/fw.c:6758 process_one_work kernel/workqueue.c:3241 worker_thread kernel/workqueue.c:3400 kthread kernel/kthread.c:463 ret_from_fork arch/x86/kernel/process.c:154 ret_from_fork_asm arch/x86/entry/entry_64.S:258

kfence-#251: 0x0000000056e2393d-0x000000009943cb62, size=232, cache=skbuff_head_cache

allocated by task 41377 on cpu 6 at 77869.159548s (0.009551s ago): __alloc_skb net/core/skbuff.c:659 __netdev_alloc_skb net/core/skbuff.c:734 ieee80211_nullfunc_get net/mac80211/tx.c:5844 rtw89_core_send_nullfunc drivers/net/wireless/realtek/rtw89/core.c:3431 rtw89_core_scan_complete drivers/net/wireless/realtek/rtw89/core.c:5338 rtw89_hw_scan_complete_cb drivers/net/wireless/realtek/rtw89/fw.c:7979 rtw89_chanctx_proceed_cb drivers/net/wireless/realtek/rtw89/chan.c:3165 rtw89_chanctx_proceed drivers/net/wireless/realtek/rtw89/chan.c:3194 rtw89_hw_scan_complete drivers/net/wireless/realtek/rtw89/fw.c:8012 rtw89_mac_c2h_scanofld_rsp drivers/net/wireless/realtek/rtw89/mac.c:5059 rtw89_fw_c2h_work drivers/net/wireless/realtek/rtw89/fw.c:6758 process_one_work kernel/workqueue.c:3241 worker_thread kernel/workqueue.c:3400 kthread kernel/kthread.c:463 ret_from_fork arch/x86/kernel/process.c:154 ret_from_fork_asm arch/x86/entry/entry_64.S:258

freed by task 1045 on cpu 9 at 77869.168393s (0.001557s ago): ieee80211_tx_status_skb net/mac80211/status.c:1117 rtw89_pci_release_txwd_skb drivers/net/wireless/realtek/rtw89/pci.c:564 rtw89_pci_release_tx_skbs.isra.0 drivers/net/wireless/realtek/rtw89/pci.c:651 rtw89_pci_release_tx drivers/net/wireless/realtek/rtw89/pci.c:676 rtw89_pci_napi_poll drivers/net/wireless/realtek/rtw89/pci.c:4238 __napi_poll net/core/dev.c:7495 net_rx_action net/core/dev.c:7557 net/core/dev.c:7684 handle_softirqs kernel/softirq.c:580 do_softirq.part.0 kernel/softirq.c:480 __local_bh_enable_ip kernel/softirq.c:407 rtw89_pci_interrupt_threadfn drivers/net/wireless/realtek/rtw89/pci.c:927 irq_thread_fn kernel/irq/manage.c:1133 irq_thread kernel/irq/manage.c:1257 kthread kernel/kthread.c:463 ret_from_fork arch/x86/kernel/process.c:154 ret_from_fork_asm arch/x86/entry/entry_64.S:258

It is a consequence of a race between the waiting and the signaling side of the completion:

Waiting thread Completing thread

rtw89_core_tx_kick_off_and_wait() rcu_assign_pointer(skb_data->wait, wait) /* start waiting */ wait_for_completion_timeout() rtw89_pci_tx_status() rtw89_core_tx_wait_complete() rcu_read_lock() /* signals completion and ---truncated---

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.3%
EPSS %ILE
19th
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.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

October 15, 2025

Last Modified

October 19, 2026

Advisory Details (4)

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

wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/895cccf639ac015f3d5f993218cf098db82ac145
Web page

wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e31a6bc07312b448fad3b45de578471f86f0e77

Vendor Advisories for CVE-2025-40000(2)

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

Patch Availability(11)

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.38-1 ... 6.12.57-1~bpo12+1 (6 versions)
  • every version up to 6.12.57-1: fixed in 6.12.57-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (71 versions)
  • every version up to 6.16.12-1: fixed in 6.16.12-1
—

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 10× in last 7d / 50× 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 98 of 243 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-40000?
CVE-2025-40000 is a high-severity vulnerability; its CVE record was published on October 15, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() There is a bug observed when rtw89_core_tx_kick_off_and_wait() tries to access already freed skb_data: BUG: KFENCE: use-after-free write in…
When was the CVE record for CVE-2025-40000 published?
The CVE record for CVE-2025-40000 was published on October 15, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2025-40000 actively exploited?
CVE-2025-40000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-40000?
CVE-2025-40000 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-40000?
A fix for CVE-2025-40000 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-40000 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-40000

Explore →

Is Your Infrastructure Affected by CVE-2025-40000?

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