CVE-2026-23454

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-04-03. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

A fix is available — apply it.

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

net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown

A potential race condition exists in mana_hwc_destroy_channel() where hwc->caller_ctx is freed before the HWC's Completion Queue (CQ) and Event Queue (EQ) are destroyed. This allows an in-flight CQ interrupt handler to dereference freed memory, leading to a use-after-free or NULL pointer dereference in mana_hwc_handle_resp().

mana_smc_teardown_hwc() signals the hardware to stop but does not synchronize against IRQ handlers already executing on other CPUs. The IRQ synchronization only happens in mana_hwc_destroy_cq() via mana_gd_destroy_eq() -> mana_gd_deregister_irq(). Since this runs after kfree(hwc->caller_ctx), a concurrent mana_hwc_rx_event_handler() can dereference freed caller_ctx (and rxq->msg_buf) in mana_hwc_handle_resp().

Fix this by reordering teardown to reverse-of-creation order: destroy the TX/RX work queues and CQ/EQ before freeing hwc->caller_ctx. This ensures all in-flight interrupt handlers complete before the memory they access is freed.

CVSS v3
7.0
EG Score
7.0(medium)
EPSS
2.2%
KEV
Not listed

Published

April 3, 2026

Last Modified

July 14, 2026

Advisory Details (9)

Auto-updated Jul 14, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b001901f689021acd7bf2dceed74a1bdcaaa1f9
generic

net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/249e905571583a434d4ea8d6f92ccc0eef337115
generic

net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05d345719d85b927cba74afac4d5322de3aa4256

Vendor Advisories for CVE-2026-23454(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-6.17 (6.17.0-1015.15) @ questing2026-06-11ubuntu
linuxKernel @ 5.15.203osv

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

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 12× in last 7d / 46× 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.

Showing the most recent 100 of 115 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23454?
CVE-2026-23454 is a high vulnerability published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mana: fix use-after-free in manahwcdestroy_channel() by reordering teardown A potential race condition exists in manahwcdestroy_channel() where hwc->caller_ctx is freed before the HWC's Completion Queue (CQ) and Event Queue…
When was CVE-2026-23454 disclosed?
CVE-2026-23454 was first published in the National Vulnerability Database on April 3, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23454 actively exploited?
CVE-2026-23454 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23454?
CVE-2026-23454 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-23454?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23454, 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-23454

Explore →

Is Your Infrastructure Affected by CVE-2026-23454?

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