CVE-2025-21730

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-02-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-5226 (ENISA EUVD) · GHSA-cg84-5crp-xcxj (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: rtw89: avoid to init mgnt_entry list twice when WoWLAN failed

If WoWLAN failed in resume flow, the rtw89_ops_add_interface() triggered without removing the interface first. Then the mgnt_entry list init again, causing the list_empty() check in rtw89_chanctx_ops_assign_vif() useless, and list_add_tail() again. Therefore, we have added a check to prevent double adding of the list.

rtw89_8852ce 0000:01:00.0: failed to check wow status disabled rtw89_8852ce 0000:01:00.0: wow: failed to check disable fw ready rtw89_8852ce 0000:01:00.0: wow: failed to swap to normal fw rtw89_8852ce 0000:01:00.0: failed to disable wow rtw89_8852ce 0000:01:00.0: failed to resume for wow -110 rtw89_8852ce 0000:01:00.0: MAC has already powered on i2c_hid_acpi i2c-ILTK0001:00: PM: acpi_subsys_resume+0x0/0x60 returned 0 after 284705 usecs list_add corruption. prev->next should be next (ffff9d9719d82228), but was ffff9d9719f96030. (prev=ffff9d9719f96030). ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:34! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 2 PID: 6918 Comm: kworker/u8:19 Tainted: G U O Hardware name: Google Anraggar/Anraggar, BIOS Google_Anraggar.15217.514.0 03/25/2024 Workqueue: events_unbound async_run_entry_fn RIP: 0010:__list_add_valid_or_report+0x9f/0xb0 Code: e8 56 89 ff ff 0f 0b 48 c7 c7 3e fc e0 96 48 89 c6 e8 45 89 ff ... RSP: 0018:ffffa51b42bbbaf0 EFLAGS: 00010246 RAX: 0000000000000075 RBX: ffff9d9719d82ab0 RCX: 13acb86e047a4400 RDX: 3fffffffffffffff RSI: 0000000000000000 RDI: 00000000ffffdfff RBP: ffffa51b42bbbb28 R08: ffffffff9768e250 R09: 0000000000001fff R10: ffffffff9765e250 R11: 0000000000005ffd R12: ffff9d9719f95c40 R13: ffff9d9719f95be8 R14: ffff9d97081bfd78 R15: ffff9d9719d82060 FS: 0000000000000000(0000) GS:ffff9d9a6fb00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007e7d029a4060 CR3: 0000000345e38000 CR4: 0000000000750ee0 PKRU: 55555554 Call Trace: ? __die_body+0x68/0xb0 ? die+0xaa/0xd0 ? do_trap+0x9f/0x170 ? __list_add_valid_or_report+0x9f/0xb0 ? __list_add_valid_or_report+0x9f/0xb0 ? handle_invalid_op+0x69/0x90 ? __list_add_valid_or_report+0x9f/0xb0 ? exc_invalid_op+0x3c/0x50 ? asm_exc_invalid_op+0x16/0x20 ? __list_add_valid_or_report+0x9f/0xb0 rtw89_chanctx_ops_assign_vif+0x1f9/0x210 [rtw89_core cbb375c44bf28564ce479002bff66617a25d9ac1] ? __mutex_unlock_slowpath+0xa0/0xf0 rtw89_ops_assign_vif_chanctx+0x4b/0x90 [rtw89_core cbb375c44bf28564ce479002bff66617a25d9ac1] drv_assign_vif_chanctx+0xa7/0x1f0 [mac80211 6efaad16237edaaea0868b132d4f93ecf918a8b6] ieee80211_reconfig+0x9cb/0x17b0 [mac80211 6efaad16237edaaea0868b132d4f93ecf918a8b6] ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 572d03acaaa933fe38251be7fce3b3675284b8ed] ? dev_printk_emit+0x51/0x70 ? _dev_info+0x6e/0x90 wiphy_resume+0x89/0x180 [cfg80211 572d03acaaa933fe38251be7fce3b3675284b8ed] ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 572d03acaaa933fe38251be7fce3b3675284b8ed] dpm_run_callback+0x37/0x1e0 device_resume+0x26d/0x4b0 ? __pfx_dpm_watchdog_handler+0x10/0x10 async_resume+0x1d/0x30 async_run_entry_fn+0x29/0xd0 worker_thread+0x397/0x970 kthread+0xed/0x110 ? __pfx_worker_thread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x38/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.2%
EPSS %ILE
8th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

February 27, 2025

Last Modified

August 5, 2026

Advisory Details (3)

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

wifi: rtw89: avoid to init mgnt_entry list twice when WoWLAN failed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7fc295fdd3992a9a07d12fd3f2e84dface23aedc
Web page

wifi: rtw89: avoid to init mgnt_entry list twice when WoWLAN failed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ed5bf49819757303e657f3900725febf2f3926f
Web page

wifi: rtw89: avoid to init mgnt_entry list twice when WoWLAN failed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f7667675df1b40b73ecc53b4b8c3189b1e5f2c1

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.13.2 (fixes >=6.13.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
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2025-21730?
CVE-2025-21730 is a medium-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: avoid to init mgnt_entry list twice when WoWLAN failed If WoWLAN failed in resume flow, the rtw89_ops_add_interface() triggered without removing the interface first. Then the mgnt_entry list init again, causing the…
When was the CVE record for CVE-2025-21730 published?
The CVE record for CVE-2025-21730 was published on February 27, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-21730 actively exploited?
CVE-2025-21730 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21730?
CVE-2025-21730 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21730?
A fix for CVE-2025-21730 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-21730?

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

Book a Demo →Browse All CVEs