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

CVE record · `CVE-2026-43276`

- **Identifiers:** `CVE-2026-43276`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 6 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 6 May 2026, 11:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `505cc26bcae00699bacaee66cd50ede7a9cc89cb to before fa3c2f8d9152344a478abb847081c1b5f84a94f5` (git)
  - affected: `505cc26bcae00699bacaee66cd50ede7a9cc89cb to before a9a7c3203fdc4d4a8d8a7a3b1ed05d2bb4c6e77e` (git)
  - affected: `505cc26bcae00699bacaee66cd50ede7a9cc89cb to before f975a0955276579e2176a134366ed586071c7c6a` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.16`
  - unaffected: `before 6.16` (semver)
  - unaffected: `6.18.16 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.6 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The mana network driver in the Linux kernel is affected from version 6.16 up to, but not including, 6.18.16 in the 6.18 series and 6.19.6 in the 6.19 series. A double workqueue destroy on the PCI service rescan path after a failed resume causes a use-after-free crash, and the source gives few details on what triggers it or who can trigger it. Upgrade to Linux kernel 6.18.16, 6.19.6, 7.0 or a later fixed version.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 6 May 2026, 11:28 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43276)
- 6 May 2026, 12:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43276)

## Sources

- [CVE List: CVE-2026-43276](https://www.cve.org/CVERecord?id=CVE-2026-43276)
- [NVD: CVE-2026-43276](https://nvd.nist.gov/vuln/detail/CVE-2026-43276)

### References from the CNA

- <https://git.kernel.org/stable/c/fa3c2f8d9152344a478abb847081c1b5f84a94f5>
- <https://git.kernel.org/stable/c/a9a7c3203fdc4d4a8d8a7a3b1ed05d2bb4c6e77e>
- <https://git.kernel.org/stable/c/f975a0955276579e2176a134366ed586071c7c6a>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43276>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43276/>. Everything for agents: <https://agentprime.io/llms.txt>.
