# CVE-2026-72495: RDMA/bnxt_re: Avoid repeated requests to allocate WC pages

> A race condition in the Linux kernel RDMA driver allows repeated WC page allocation requests, potentially leading to resource exhaustion or denial of service.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 21 Oct 2026
- **Also known as:** AZL-96081, BELL-CVE-2026-72495, DEBIAN-CVE-2026-72495, GHSA-3cmq-754m-66f5, UBUNTU-CVE-2026-72495

## What is CVE-2026-72495?

CVE-2026-72495 is a critical 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/bnxt_re: Avoid repeated requests to allocate WC pages

Applications can request multiple WC pages for the same ucontext.
As of now, only 1 WC page per ucontext is supported. Add a lock to
avoid concurrent access and a check to fail repeated requests.
Also, if the mmap entry insert fails for the WC, free the Doorbell
page index mapped for the WC page.

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


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

Apply the vendor's patch.

## Is CVE-2026-72495 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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