CVE-2026-45910·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix race condition in QP timer handlers I encontered the following warning: WARNING: drivers/infiniband/sw/rxe/rxe_task.c:249 at rxe_sched_task+0x1c8/0x238 [rdma_rxe], CPU#0: swapper/0/0 ... libsha1 [last unloaded: ip6_udp_tunnel] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Tainted: G C 6.19.0-rc5-64k-v8+ #37 PREEMPT Tainted: [C]=CRAP Hardware name: Raspberry Pi 4 Model B Rev 1.2 Call trace: rxe_sched_task+0x1c8/0x238 [rdma_rxe] (P) retransmit_timer+0x130/0x188 [rdma_rxe] call_timer_fn+0x68/0x4d0 __run_timers+0x630/0x888 ... WARNING: drivers/infiniband/sw/rxe/rxe_task.c:38 at rxe_sched_task+0x1c0/0x238 [rdma_rxe], CPU#0: swapper/0/0 ... WARNING: drivers/infiniband/sw/rxe/rxe_task.c:111 at do_work+0x488/0x5c8 [rdma_rxe], CPU#3: kworker/u17:4/93400 ... refcount_t: underflow; use-after-free. WARNING: lib/refcount.c:28 at refcount_warn_saturate+0x138/0x1a0, CPU#3: kworker/u17:4/93400 The issue is caused by a race condition between retransmit_timer() and rxe_destroy_qp, leading to the Queue Pair's (QP) reference count dropping to zero during timer handler execution. It seems this warning is harmless because rxe_qp_do_cleanup() will flush all pending timers and requests. Example of flow causing the issue: CPU0 CPU1 retransmit_timer() { spin_lock_irqsave rxe_destroy_qp() __rxe_cleanup() __rxe_put() // qp->ref_count decrease to 0 rxe_qp_do_cleanup() { if (qp->valid) { rxe_sched_task() { WARN_ON(rxe_read(task->qp) <= 0); } } spin_unlock_irqrestore } spin_lock_irqsave qp->valid = 0 spin_unlock_irqrestore } Ensure the QP's reference count is maintained and its validity is checked within the timer callbacks by adding calls to rxe_get(qp) and corresponding rxe_put(qp) after use.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.4
- Published
Affected versions
From: 6.19
Until: 6.19.4
Fixed in: 6.19.4
How to fix this CVE
Update your Linux kernel to version 6.19.4 or later to resolve a race condition in RDMA/RXE QP timer handlers that can cause reference count underflows and use-after-free conditions. This fix ensures proper reference counting and validity checks within timer callbacks to prevent kernel warnings and potential memory corruption during queue pair destruction.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with `uname -r` and confirm if it falls in the 6.19.0 to 6.19.3 range
- Step 2: Verify if RDMA/RXE module is loaded: `lsmod | grep rdma_rxe` or `modinfo rdma_rxe`
- Step 3: Search kernel logs for race condition indicators: `dmesg | grep -i 'refcount\|underflow\|use-after-free\|rxe_sched_task'` or `journalctl -k | grep -i 'rxe\|refcount'`
- Step 4: After patching, reboot and verify the new kernel version: `uname -r` should show 6.19.4 or later, then confirm no RDMA warnings appear in `dmesg` during QP operations
FAQ
What is CVE-2026-45910?
This vulnerability is a race condition in the Linux kernel's RDMA/RXE (software RDMA) subsystem where concurrent execution of QP timer handlers and QP destruction routines can cause the queue pair's reference count to drop to zero prematurely, leading to use-after-free conditions and kernel warnings.
Is CVE-2026-45910 being actively exploited?
No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, it can cause kernel instability and data corruption in RDMA-based workloads.
What versions of Kernel are affected by CVE-2026-45910?
Linux kernel versions 6.19.0 through 6.19.3 are affected. The vulnerability is resolved in kernel 6.19.4 and later versions.
How do I check if my server is vulnerable to CVE-2026-45910?
Run `uname -r` to check your kernel version. If the output shows a version between 6.19.0 and 6.19.3 and RDMA/RXE is loaded (`lsmod | grep rdma_rxe`), your system is vulnerable.
Does Defensia detect CVE-2026-45910?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-45910 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/3c2ae79fb19dfd67341c14f1e78a5f1744eacfe2
- https://git.kernel.org/stable/c/5ae9da022ee3c97e6469eabcddce9271501ddbad
- https://git.kernel.org/stable/c/756c93d6df7c3bc599f6590b8e5afead6a41de1c
- https://git.kernel.org/stable/c/87bf646921430e303176edc4eb07c30160361b73
- https://git.kernel.org/stable/c/da379ca16af3722f159860d91a99cb6976a7500f
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-45910. Free for 1 server.
Get started free