CVE-2026-80947

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-11. A secondary CVSS source baseline 7.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
7.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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop

rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_list and, once the list grows past RTL8XXXU_RX_URB_PENDING_WATER, schedules rx_urb_wq. The worker rtl8xxxu_rx_urb_work() drains rx_urb_pending_list, recovers priv through container_of, and resubmits each URB through rtl8xxxu_submit_rx_urb(), which anchors it on rx_anchor and dereferences priv->udev.

rtl8xxxu_stop() cancels the sibling work items (c2hcmd_work, ra_watchdog, update_beacon_work) but never cancels rx_urb_wq, so a worker armed during the last burst of RX traffic can run rtl8xxxu_rx_urb_work() after rtl8xxxu_disconnect() has called ieee80211_free_hw(), which frees priv, producing a use-after-free. The window opens under active RX traffic (pending count above the watermark) followed by a disconnect.

There are two teardown races to close:

* rtl8xxxu_queue_rx_urb() decided whether to enqueue under rx_urb_lock but called schedule_work() after dropping the lock. A completion that observed shutdown == false and released the lock could then call schedule_work() after rtl8xxxu_stop() had set shutdown and cancel_work_sync() had already returned, arming the worker to run after the teardown. Move schedule_work() under the same !shutdown branch so the arming decision is atomic with the shutdown check.

* rtl8xxxu_rx_urb_work() anchors every URB it drained back onto rx_anchor through rtl8xxxu_submit_rx_urb(). A worker still running when usb_kill_anchored_urbs(&priv->rx_anchor) returned would submit a URB that escaped the kill. In rtl8xxxu_stop(), call cancel_work_sync(&priv->rx_urb_wq) before the kill so the worker is drained first.

After priv->shutdown is set under rx_urb_lock, completions can no longer queue rx_urb_wq. cancel_work_sync() then drains the last queued or running worker, and the following usb_kill_anchored_urbs() kills the URBs it may have submitted.

rtl8xxxu_disconnect() is covered because ieee80211_unregister_hw() guarantees .stop() runs for a live interface before ieee80211_free_hw() frees priv. The probe error path needs no cancel: rx_urb_wq is INIT_WORK()'d there but cannot have been scheduled, since no URB is submitted before ieee80211_register_hw() succeeds.

This bug was found by static analysis.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
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
5th
KEV
Not listed

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.

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

September 11, 2026

Last Modified

September 13, 2026

Advisory Details (4)

Auto-updated Sep 13, 2026
Patch available.
Web page

wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c080026ecc17eecb103f8927c64ea73a74bb818
Web page

wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/972ab8b9c08f3eb3fa535082de2950dd93604dfd
Web page

wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/620acb1e8037b73a457dc8ef20fc23fc7adcb405
Web page

wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/800d2b490a9af1e7132a3564c2ad5a81292e5b40

Vendor Advisories for CVE-2026-80947(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 35× in last 7d / 167× 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 100 of 178 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. None are among the latest 100 rows. The 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-80947?
CVE-2026-80947 is a high-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: rtl8xxxu: fix use-after-free from rxurbwq on stop rtl8xxxu arms rxurbwq from the RX completion path: rtl8xxxurxcomplete() hands the URB to rtl8xxxuqueuerx_urb(), which queues it on rxurbpending_list and, once the list grows…
When was the CVE record for CVE-2026-80947 published?
The CVE record for CVE-2026-80947 was published on September 11, 2026. 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 September 13, 2026; the record at its source may have been updated since.
Is CVE-2026-80947 actively exploited?
CVE-2026-80947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80947?
CVE-2026-80947 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80947?
A fix for CVE-2026-80947 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80947 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-2026-80947

Explore →

Is Your Infrastructure Affected by CVE-2026-80947?

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