# CVE-2026-74299: RDMA/core: Fix FRMR aging push to queue error flow

> A memory leak in the Linux kernel RDMA core allows attackers to cause denial of service by triggering failures in FRMR aging queue operations.

- **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:** DEBIAN-CVE-2026-74299, GHSA-j69g-mrr3-p2qh, UBUNTU-CVE-2026-74299

## What is CVE-2026-74299?

CVE-2026-74299 is a memory corruption 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:

RDMA/core: Fix FRMR aging push to queue error flow

Aging pools with pinned handles requires moving handles from the
active queue to a non-empty inactive queue that might fail on new page
allocation, we are currently not handling the fault and leaking any mkey
that fails the push.

Fix by Introducing push_queue_to_queue_locked() that fills the
destination's partial tail page from the source and then splices the
remaining source pages onto the destination, performing no allocation.

Replace the per-handle move loop in age_pinned_pool() and the
open-coded splice in pool_aging_work() with calls to the helper.
As the helper cannot fail under memory pressure, removing a class of
GFP_ATOMIC allocations under the pool lock and simplifying the error
flow.

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


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

Apply the vendor's patch.

## Is CVE-2026-74299 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74299 is a memory corruption 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-74299 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-74299/ (Markdown: https://insights.sbomify.com/CVE-2026-74299/index.md)
```

## Sources

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

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