Look up another CVE · open CVE-2026-72497 in the interactive tracker
CVE-2026-72497
RDMA/bnxt_re: Add a max slot check for SQ
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem drivers/infiniband. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-72497 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The variable WQE mode must be validated against the maximum slots supported by HW. The max supported value is 64K. Adding a max and min check and fail if user supplied value is more than the max supported and zero.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/infiniband/hw/bnxt_re/ib_verbs.c
drivers/infiniband/hw/bnxt_re/qplib_sp.h
- What this is
- BROADCOM NETXTREME-E ROCE DRIVERMAINTAINERS section matched on drivers/infiniband/hw/bnxt_re/ · linux-rdma@vger.kernel.org · Supported
- Kernel module
- bnxt_re
Check it on the machine
grep -wE 'CONFIG_INFINIBAND|CONFIG_INFINIBAND_BNXT_RE' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w bnxt_rePrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian does not build this code in 1 release. It does build it in 3 releases, so the answer depends on which release the machine runs.
- bookwormn
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae
- n
- not enabled on any flavour - this release does not build the code
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_INFINIBAND, CONFIG_INFINIBAND_BNXT_RE
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-15 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 6.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/infiniband
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.12 | 6.18.57 | 2106c337905d |
| 6.12 | 7.1.5 | a59d815cbe66 |
| 6.12 | 7.2 | dc95931b7e13 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The flaw is reached only via local RDMA uverbs ioctl/write on /dev/infiniband/uverbs* (IB_USER_VERBS_CMD_CREATE_QP → bnxt_re_create_qp → bnxt_re_init_qp_attr); remote RoCE peers cannot supply the bnxt_re_qp_req.sq_slots field.
- AC:LAttack complexity, low
- On bnxt_re hardware with variable WQE enabled, an attacker deterministically sets sq_slots to 0 or any value above 65536 in create_qp driver udata; no race, timing window, or uncontrollable memory layout is required beyond opening uverbs and issuing the ioctl.
- PR:LPrivileges required, low
- Exploitation requires only local access to the world-accessible (mode 0666) uverbs character device to alloc a VAR_WQE ucontext and create a QP; no CAP_SYS_ADMIN, init-namespace root, or other elevated capability is needed on typical HPC/cloud RDMA hosts.
- UI:NUser interaction, none
- The attacker triggers the bug entirely through their own alloc_context/create_qp sequence with crafted sq_slots; no cooperative action by another user, administrator, or victim is required.
- S:CScope, changed
- On Kubernetes/HPC hosts that expose bnxt_re to unprivileged RDMA workloads or containers, corrupting host-kernel memory or NIC DMA state from a tenant create_qp escapes the workload security boundary to the hypervisor/host authority.
- C:HConfidentiality impact, high
- Unvalidated sq_slots drives integer overflow in SQ/PSN byte sizing and can register undersized ib_umem while programming firmware with a far larger sq_size, enabling out-of-bounds DMA reads and kernel memory disclosure beyond the mapped queue buffer.
- I:HIntegrity impact, high
- Oversized sq_slots values program hardware queue depth beyond the registered user buffer and corrupt queue/PSN metadata sizing, yielding out-of-bounds writes and exploitable memory corruption rather than a benign error return.
- A:HAvailability impact, high
- Invalid zero or >64K slot counts can kernel-oops during QP setup (e.g., inconsistent HWQ/PSN allocation) and misprogrammed queue depths can panic or hang the host when the adapter accesses nonexistent queue memory.