CVE-2026-72489

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

staging: nvec: fix use-after-free in nvec_rx_completed()

In nvec_rx_completed(), when an incomplete RX transfer is detected, nvec_msg_free() is called to return the message back to the pool by clearing its 'used' atomic flag. Immediately after this, the code accesses nvec->rx->data[0] to check the message type.

Since nvec_msg_free() marks the pool slot as available via atomic_set(), any concurrent or subsequent call to nvec_msg_alloc() could claim that same slot and overwrite its data[] array. Reading nvec->rx->data[0] after freeing the message is therefore a use-after-free.

Fix this by saving the message type byte before calling nvec_msg_free(), then using the saved value for the battery quirk check.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

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
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

staging: nvec: fix use-after-free in nvec_rx_completed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f19a5bc059051143c489dd6f79a0f9c3bfd13aea
generic

staging: nvec: fix use-after-free in nvec_rx_completed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb3d592c7d6c4ec8ac6640c690ca13298e7e8e90
generic

staging: nvec: fix use-after-free in nvec_rx_completed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a37625c7b688fcf68a54263528eccbabfd7fa17a
generic

staging: nvec: fix use-after-free in nvec_rx_completed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f7fe4165a1f1014bdadc8e744c0fd3c2d8c0b89
generic

staging: nvec: fix use-after-free in nvec_rx_completed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b2ea886ebdae44a2394029844a4e78f58e1587d
generic

staging: nvec: fix use-after-free in nvec_rx_completed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5de04caa46b635e180cecbd164e333eca535db94
generic

staging: nvec: fix use-after-free in nvec_rx_completed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26813881181deb3a32fbb59eadb2599cbe8423f6
generic

staging: nvec: fix use-after-free in nvec_rx_completed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08626fcfe12308ca3f8b22c538ba7dee0b2dce7a

Vendor Advisories for CVE-2026-72489(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 28× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 11:39 UTCGHSA enrichment
  3. 2026-08-19 22:50 UTCEG score recompute
  4. 2026-08-19 22:50 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 10:00 UTCGHSA enrichment
  7. 2026-08-18 21:07 UTCEG score recompute
  8. 2026-08-18 21:07 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 08:16 UTCGHSA enrichment
  12. 2026-08-17 19:17 UTCEG score recompute
  13. 2026-08-17 19:17 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:27 UTCEG score recompute
  16. 2026-08-17 06:27 UTCGHSA enrichment
  17. 2026-08-17 05:57 UTCEG score recompute▲ 8.40
  18. 2026-08-17 05:57 UTCGHSA enrichment
  19. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  20. 2026-08-17 05:28 UTCEG score recompute
  21. 2026-08-17 05:28 UTCGHSA enrichment
  22. 2026-08-17 05:24 UTCMITRE cvelistV5
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 3 more
  1. 2026-08-15 06:23 UTCNVD update
  2. 2026-08-15 06:03 UTCEG score recompute
  3. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72489?
CVE-2026-72489 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: staging: nvec: fix use-after-free in nvecrxcompleted() In nvecrxcompleted(), when an incomplete RX transfer is detected, nvecmsgfree() is called to return the message back to the pool by clearing its 'used' atomic flag. Immediately…
When was CVE-2026-72489 disclosed?
CVE-2026-72489 was first published in the National Vulnerability Database on August 15, 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-72489 actively exploited?
CVE-2026-72489 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 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-72489?
CVE-2026-72489 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-72489?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72489, 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

Explore the affected products and dependency analysis for CVE-2026-72489

Explore →

Is Your Infrastructure Affected by CVE-2026-72489?

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

Start Free Scan →Browse All CVEs