Look up another CVE · open CVE-2025-21885 in the interactive tracker
CVE-2025-21885
RDMA/bnxt_re: Fix the page details for the srq created by kernel consumers
Published 2025-03-27 (19 months ago) by the Linux kernel CNA. Subsystem drivers/infiniband. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2025-21885 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 | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.12.19-1 | Update the kernel and reboot. Fixed in 6.12.19-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.12.19-1 | Update the kernel and reboot. Fixed in 6.12.19-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.12.19-1 | Update the kernel and reboot. Fixed in 6.12.19-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
While using nvme target with use_srq on, below kernel panic is noticed. [ 549.698111] bnxt_en 0000:41:00.0 enp65s0np0: FEC autoneg off encoding: Clause 91 RS(544,514) [ 566.393619] Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI .. [ 566.393799] <TASK> [ 566.393807] ? __die_body+0x1a/0x60 [ 566.393823] ? die+0x38/0x60 [ 566.393835] ? do_trap+0xe4/0x110 [ 566.393847] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393867] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393881] ? do_error_trap+0x7c/0x120 [ 566.393890] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393911] ? exc_divide_error+0x34/0x50 [ 566.393923] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393939] ? asm_exc_divide_error+0x16/0x20 [ 566.393966] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393997] bnxt_qplib_create_srq+0xc9/0x340 [bnxt_re] [ 566.394040] bnxt_re_create_srq+0x335/0x3b0 [bnxt_re] [ 566.394057] ? srso_return_thunk+0x5/0x5f [ 566.394068] ? __init_swait_queue_head+0x4a/0x60 [ 566.394090] ib_create_srq_user+0xa7/0x150 [ib_core] [ 566.394147] nvmet_rdma_queue_connect+0x7d0/0xbe0 [nvmet_rdma] [ 566.394174] ? lock_release+0x22c/0x3f0 [ 566.394187] ? srso_return_thunk+0x5/0x5f Page size and shift info is set only for the user space SRQs. Set page size and page shift for kernel space SRQs also.
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
- 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
- 2025-03-27 (19 months ago)source
- CVSS
- 7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.43%, higher than 36.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- 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 |
|---|---|---|
| 5.7 | 6.12.18 | 722c3db62bf6 |
| 5.7 | 6.13.6 | 2cf8e6b52aec |
| 5.7 | 6.14 | b66535356a48 |
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:NAttack vector, network
- The crash is reached from `nvmet_rdma_queue_connect()`, the handler for an inbound RDMA CM connect request on the NVMe-oF target's listening endpoint; bnxt_re is a RoCE device and RoCEv2 is UDP/IP-encapsulated and fully routable, so a remote off-segment initiator can drive the path.
- AC:LAttack complexity, low
- The divide-by-zero is deterministic — `sg_info.pgsize` is unconditionally 0 for every kernel-created SRQ — so the very first connect request from the attacker triggers it with no race, timing, or memory-layout dependency.
- PR:NPrivileges required, none
- SRQ allocation happens in `nvmet_rdma_find_get_device()` at the top of the connect-request handler, before the NVMe fabrics Connect command, host-NQN allow-list checks, or any authentication, so an entirely unauthenticated remote peer reaches it.
- UI:NUser interaction, none
- The target processes inbound RDMA CM connect requests autonomously; no local user or administrator action is needed once the nvmet-rdma port is listening.
- S:UScope, unchanged
- The fault is a divide error inside the kernel affecting only the host kernel's own resources, with no crossing of a VM, IOMMU, or other security authority boundary.
- C:NConfidentiality impact, none
- The zero divisor causes a `#DE` trap before any allocation, pointer arithmetic, or buffer access occurs, so no out-of-bounds read or information disclosure primitive exists.
- I:NIntegrity impact, none
- No memory is corrupted or written out of bounds — the failure is a CPU exception on the division itself, giving no write or control-flow primitive.
- A:HAvailability impact, high
- The divide error Oopses the RDMA CM workqueue thread while `device_list_mutex` and the cma `handler_mutex` are held, permanently deadlocking nvmet-rdma and RDMA connection management, and produces a full kernel panic with `panic_on_oops=1`.