KernelScan.io

HIGH Introduced in 6.6

bnxt_re DBRPage Bypass

CVE-2026-92495

CVSS 7.3 / 10.0 KernelScan AI

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

01

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.

02

Engine v0.6.0

Risk summary

A local user with access to a Broadcom NetXtreme RDMA device can bypass the driver's write protection on shared doorbell and pacing pages by upgrading a read-only mmap to writable via mprotect(). This allows unauthorized writes to device-shared memory, potentially corrupting device state and causing crashes or hangs. Systems exposing RDMA devices to untrusted or containerized workloads are at highest risk.

Affecteddrivers/infiniband/hw/bnxt_re/ib_verbs.c (RDMA/bnxt_re)

Vulnerability analysis

The driver shares doorbell and pacing pages with userspace but only checks for unwanted writable access when the initial memory mapping is created. Because the mapping is still internally flagged as allowed to become writable, a process can later upgrade it to write access using standard system calls to change memory permissions, bypassing the restriction entirely. The fix removes that upgrade permission before the page is inserted into the process address space, so the mapping stays read-only. Any local process that can open the Broadcom NetXtreme RDMA device can reach this flaw; whether ordinary users can trigger it depends on the device file permissions. Gaining write access allows corruption of device-shared state and can crash or hang the adapter.

03

BranchIntroducedFixed inPatch commit
6.126.66.12.11013e7861809ef
6.186.66.18.520afbfe019c88
6.66.66.6.1575361fb1e5bc2
7.26.67.2.6518df61b9b0a
mainline6.67.39b66c9af7172
cip/6.126.66.12.111-cip3213e7861809ef

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.111-cip32