CVE-2026-43276

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

net: mana: Fix double destroy_workqueue on service rescan PCI path

While testing corner cases in the driver, a use-after-free crash was found on the service rescan PCI path.

When mana_serv_reset() calls mana_gd_suspend(), mana_gd_cleanup() destroys gc->service_wq. If the subsequent mana_gd_resume() fails with -ETIMEDOUT or -EPROTO, the code falls through to mana_serv_rescan() which triggers pci_stop_and_remove_bus_device(). This invokes the PCI .remove callback (mana_gd_remove), which calls mana_gd_cleanup() a second time, attempting to destroy the already- freed workqueue. Fix this by NULL-checking gc->service_wq in mana_gd_cleanup() and setting it to NULL after destruction.

Call stack of issue for reference: [Sat Feb 21 18:53:48 2026] Call Trace: [Sat Feb 21 18:53:48 2026] [Sat Feb 21 18:53:48 2026] mana_gd_cleanup+0x33/0x70 [mana] [Sat Feb 21 18:53:48 2026] mana_gd_remove+0x3a/0xc0 [mana] [Sat Feb 21 18:53:48 2026] pci_device_remove+0x41/0xb0 [Sat Feb 21 18:53:48 2026] device_remove+0x46/0x70 [Sat Feb 21 18:53:48 2026] device_release_driver_internal+0x1e3/0x250 [Sat Feb 21 18:53:48 2026] device_release_driver+0x12/0x20 [Sat Feb 21 18:53:48 2026] pci_stop_bus_device+0x6a/0x90 [Sat Feb 21 18:53:48 2026] pci_stop_and_remove_bus_device+0x13/0x30 [Sat Feb 21 18:53:48 2026] mana_do_service+0x180/0x290 [mana] [Sat Feb 21 18:53:48 2026] mana_serv_func+0x24/0x50 [mana] [Sat Feb 21 18:53:48 2026] process_one_work+0x190/0x3d0 [Sat Feb 21 18:53:48 2026] worker_thread+0x16e/0x2e0 [Sat Feb 21 18:53:48 2026] kthread+0xf7/0x130 [Sat Feb 21 18:53:48 2026] ? __pfx_worker_thread+0x10/0x10 [Sat Feb 21 18:53:48 2026] ? __pfx_kthread+0x10/0x10 [Sat Feb 21 18:53:48 2026] ret_from_fork+0x269/0x350 [Sat Feb 21 18:53:48 2026] ? __pfx_kthread+0x10/0x10 [Sat Feb 21 18:53:48 2026] ret_from_fork_asm+0x1a/0x30 [Sat Feb 21 18:53:48 2026]

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 8, 2026

Advisory Details (3)

Auto-updated May 8, 2026
No patch confirmed yet.
generic

net: mana: Fix double destroy_workqueue on service rescan PCI path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: Fix double destroy_workqueue on service rescan PCI path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: Fix double destroy_workqueue on service rescan PCI path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a9a7c3203fdc4d4a8d8a7a3b1ed05d2bb4c6e77e

Vendor Advisories for CVE-2026-43276(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-6.17 (6.17.0-1015.15) @ questing2026-08-23ubuntu
redhatkernel-0:6.12.0-211.31.1.el10_22026-07-08redhat
redhatkernel-0:5.14.0-687.22.1.el9_82026-07-06redhat
linuxKernel @ 6.18.16—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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× 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.

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

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43276?
CVE-2026-43276 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix double destroy_workqueue on service rescan PCI path While testing corner cases in the driver, a use-after-free crash was found on the service rescan PCI path. When manaservreset() calls managdsuspend(),…
When was CVE-2026-43276 disclosed?
CVE-2026-43276 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43276 actively exploited?
CVE-2026-43276 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 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43276?
CVE-2026-43276 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43276?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43276, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43276

Explore →

Is Your Infrastructure Affected by CVE-2026-43276?

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

Start Free Scan →Browse All CVEs