Skip to main content
VulnerabilityPublished Updated

CVE-2026-23454: Linux kernel · net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fa103fc8f56954a60699a29215cb713448a39e87 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 22:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in fa103fc8f56954a60699a29215cb713448a39e87, e23bf444512cb85d76012080a76cd1f9e967448e, b88edf12fc3779521ae5f6f1584153b15f7da6df +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < fa103fc8f56954a60699a29215cb713448a39e87
Fixed in
  • fa103fc8f56954a60699a29215cb713448a39e87
LinuxLinuxAffected
  • ≥ ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < e23bf444512cb85d76012080a76cd1f9e967448e
Fixed in
  • e23bf444512cb85d76012080a76cd1f9e967448e
LinuxLinuxAffected
  • ≥ ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < b88edf12fc3779521ae5f6f1584153b15f7da6df
Fixed in
  • b88edf12fc3779521ae5f6f1584153b15f7da6df
LinuxLinuxAffected
  • ≥ ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < afdb1533eb9c05432aeb793a7280fa827c502f5c
Fixed in
  • afdb1533eb9c05432aeb793a7280fa827c502f5c
LinuxLinuxAffected
  • ≥ ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < 249e905571583a434d4ea8d6f92ccc0eef337115
Fixed in
  • 249e905571583a434d4ea8d6f92ccc0eef337115
LinuxLinuxAffected
  • ≥ ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < 05d345719d85b927cba74afac4d5322de3aa4256
Fixed in
  • 05d345719d85b927cba74afac4d5322de3aa4256

Description

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.

References

Community reviews

Loading reviews…