# CVE-2026-74265: net: mana: initialize gdma queue id to INVALID_QUEUE_ID

> A flaw in the Linux kernel's MANA network driver allows a local attacker to cause a denial of service by triggering a cleanup path that corrupts queue table entries.

- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74265, DEBIAN-CVE-2026-74265, GHSA-3qw4-v9v4-3ww5, UBUNTU-CVE-2026-74265

## What is CVE-2026-74265?

CVE-2026-74265 is a vulnerability in Linux, published on 15 Aug 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: initialize gdma queue id to INVALID_QUEUE_ID

mana_gd_create_mana_wq_cq() leaves queue->id as 0 (from kzalloc_obj())
until mana_create_wq_obj() assigns the firmware-returned id. If creation
fails before that, cleanup calls mana_gd_destroy_cq() with id 0, NULLing
gc->cq_table[0] and silently breaking whichever real CQ owns that slot.

Initialize queue->id to INVALID_QUEUE_ID right after allocation, matching
mana_gd_create_eq(). The existing (id >= max_num_cqs) guard then
short-circuits cleanly.

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


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

Apply the vendor's patch.

## Is CVE-2026-74265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74265 is a vulnerability in Linux, published on 15 Aug 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-74265 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-74265/ (Markdown: https://insights.sbomify.com/CVE-2026-74265/index.md)
```

## Sources

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

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