# CVE-2026-92495: RDMA/bnxt_re: Clear VM_MAYWRITE on DBR/toggle page mmap

> Local attackers can bypass write restrictions on RDMA driver memory pages via mprotect, potentially leading to privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102434, BELL-CVE-2026-92495, DEBIAN-CVE-2026-92495, GHSA-mw3g-rrrf-x4m2, UBUNTU-CVE-2026-92495

## What is CVE-2026-92495?

CVE-2026-92495 is a vulnerability in Linux, published on 17 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:

RDMA/bnxt_re: Clear VM_MAYWRITE on DBR/toggle page mmap

bnxt_re_mmap() rejects VM_WRITE for the DBR_PAGE and TOGGLE_PAGE mmap
flags, but a read-only mapping can still retain VM_MAYWRITE. nd later
be upgraded with mprotect(PROT_WRITE). This can bypass the write check
that only runs at mmap time.

Clear VM_MAYWRITE before vm_insert_page() in the shared DBR/toggle-page
branch, matching the existing policy that userspace writes are not
expected for these pages.

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


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

Apply the vendor's patch.

## Is CVE-2026-92495 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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