# CVE-2026-97613: net: mana: Reserve extra CQ slot for the fence completion CQE

> A missing CQ slot reservation in the Linux kernel MANA driver can cause dropped fence completions and system hangs, requiring a kernel patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104832, BELL-CVE-2026-97613, DEBIAN-CVE-2026-97613, GHSA-7qp2-8vhf-pgwx, UBUNTU-CVE-2026-97613

## What is CVE-2026-97613?

CVE-2026-97613 is a denial of service vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

net: mana: Reserve extra CQ slot for the fence completion CQE

The RX completion queue is sized to hold exactly one CQE per posted RX WQE.
MANA_FENCE_RQ makes hardware post an additional CQE_RX_OBJECT_FENCE after
the packet CQEs. The current sizing reserves no extra slot for it and in
rare cases, CQ has no guaranteed slot for the fence CQE when it is full of
packet CQEs. This can lead to dropping the fence completion while the
driver waits holding RTNL lock throughout the timeout duration.
Reserve one extra CQE slot for CQE_RX_OBJECT_FENCE. mana_gd_alloc_memory()
requires queue_size to be a power-of-two and at least MANA_PAGE_SIZE;
the reservation pushes cq_size past a power-of-two, so round up the CQ size
in mana_create_rxq().

## Which versions are affected by CVE-2026-97613?


## How do I fix CVE-2026-97613?

Apply the vendor's patch.

## Is CVE-2026-97613 being exploited?

There is no known exploitation of CVE-2026-97613 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97613 and fix it if it is affected.

What it is: CVE-2026-97613 is a denial of service vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97613 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97613/ (Markdown: https://insights.sbomify.com/CVE-2026-97613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97613
- OSV: https://osv.dev/vulnerability/CVE-2026-97613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97613/
Summaries are generated and may contain mistakes; the official description above is the record.