Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97477 Overview
CVE-2026-97477 is a resource leak in the Linux kernel's Remote Direct Memory Access (RDMA) counter subsystem. The flaw lives in alloc_and_bind() within the RDMA counter code path. When __rdma_counter_bind_qp() fails, the error path jumps to err_mode and frees the counter without decrementing port_counter->num_counters. The only decrement occurs in rdma_counter_free(), which is unreachable because the counter was never successfully bound. Repeated bind failures accumulate stale counter references, permanently blocking the port from switching to AUTO mode and preventing the MANUAL→NONE auto-revert.
Critical Impact
The leak permanently blocks RDMA port mode transitions, returning -EBUSY in __counter_set_mode() and leaving ports stuck in incorrect counter modes until reboot.
Affected Products
- Linux kernel RDMA/counter subsystem
- Stable kernel branches prior to the fix commits 4fbc8230009f and da95cb016812
- Systems using RDMA Queue Pair (QP) counter binding with manual counter mode
Discovery Timeline
- 2026-09-24 - CVE-2026-97477 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-97477
Vulnerability Analysis
The vulnerability resides in alloc_and_bind() in the Linux kernel RDMA counter subsystem. The function increments port_counter->num_counters before attempting to bind a Queue Pair (QP) to a counter via __rdma_counter_bind_qp(). When the bind operation fails, control transfers to the err_mode label, which frees the counter but never decrements the previously incremented num_counters field.
The decrement logic lives exclusively in rdma_counter_free(). That function is only invoked for counters that completed binding successfully. Counters that fail during allocation and bind therefore leave num_counters permanently inflated. Each failure increases the stale count.
Once num_counters holds residual values, __counter_set_mode() rejects transitions to AUTO mode with -EBUSY. The MANUAL→NONE auto-revert path in rdma_counter_free() is also skipped. If the port mode was NONE before the failed call, the MANUAL mode set by __counter_set_mode() leaks as well because the revert logic never executes.
Root Cause
The root cause is an incomplete cleanup path. The err_mode error label frees the counter object but omits the paired decrement of port_counter->num_counters. The code relies on rdma_counter_free() for the decrement, yet that function is unreachable when binding fails before completion. This is a classic resource accounting leak [CWE-401].
Attack Vector
The condition is reached through RDMA counter bind operations that trigger __rdma_counter_bind_qp() failures. A local user or workload that repeatedly fails QP counter binds can accumulate stale num_counters values. The outcome is denial of service against the RDMA counter management interface rather than code execution or privilege escalation. No remote network exploitation vector is documented for this flaw.
The upstream fix adds an err_bind label between the num_counters increment and the existing err_mode label. The new label decrements num_counters and mirrors the MANUAL→NONE revert from rdma_counter_free(), restoring port state on bind failure. See the patch commits 4fbc8230009f and da95cb016812.
Detection Methods for CVE-2026-97477
Indicators of Compromise
- Repeated -EBUSY return values from RDMA sysfs or netlink interfaces when attempting to switch counter mode to AUTO.
- RDMA ports stuck in MANUAL mode despite administrative attempts to transition to AUTO or NONE.
- Elevated num_counters values on RDMA ports that do not match the number of actively bound Queue Pairs.
Detection Strategies
- Audit running kernel versions against the fix commits 4fbc8230009f and da95cb016812 on hosts with RDMA-capable hardware (InfiniBand, RoCE, iWARP).
- Monitor kernel logs for RDMA counter binding failures correlated with subsequent mode-change rejections.
- Inventory systems running RDMA workloads such as NVMe-oF, GPUDirect, or MPI clusters that exercise counter binding frequently.
Monitoring Recommendations
- Track RDMA port counter state via /sys/class/infiniband/*/ports/*/counters/ and alert on anomalous num_counters growth.
- Collect kernel ring buffer messages via centralized logging and search for RDMA counter bind failures.
- Use an endpoint telemetry solution to track kernel version drift across the RDMA fleet and flag unpatched hosts.
How to Mitigate CVE-2026-97477
Immediate Actions Required
- Identify all Linux hosts with RDMA hardware and determine the running kernel version using uname -r.
- Apply the upstream stable kernel updates containing commits 4fbc8230009f and da95cb016812 as soon as distribution packages are available.
- Restart affected hosts after patching to clear any accumulated stale num_counters state.
Patch Information
The fix is available in the upstream Linux stable tree. Two commits resolve the leak: Kernel Git Commit 4fbc823 and Kernel Git Commit da95cb01. Apply the vendor-backported kernel package from your Linux distribution once published. Red Hat Enterprise Linux, SUSE, Ubuntu, Debian, and Oracle Linux typically track RDMA subsystem fixes within standard stable update cycles.
Workarounds
- Avoid repeated manual counter bind operations on RDMA ports until the kernel is patched, since each failure accumulates leaked state.
- Restrict access to RDMA counter management interfaces to trusted administrators and workloads to limit opportunities for triggering bind failures.
- Reboot affected hosts to reset num_counters state if ports become stuck returning -EBUSY during mode transitions.
# Verify running kernel version and check for RDMA devices
uname -r
ls /sys/class/infiniband/
# Inspect current counter state on an RDMA port
cat /sys/class/infiniband/<device>/ports/<port>/counters/*
# After distribution patch is available, update and reboot
sudo apt update && sudo apt upgrade linux-image-generic # Debian/Ubuntu
sudo dnf update kernel # RHEL/Fedora
sudo reboot
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

