From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43469: xprtrdma: Decrement re_receiving on the early exit paths
Date: Fri, 8 May 2026 16:23:18 +0200 [thread overview]
Message-ID: <2026050804-CVE-2026-43469-3846@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
xprtrdma: Decrement re_receiving on the early exit paths
In the event that rpcrdma_post_recvs() fails to create a work request
(due to memory allocation failure, say) or otherwise exits early, we
should decrement ep->re_receiving before returning. Otherwise we will
hang in rpcrdma_xprt_drain() as re_receiving will never reach zero and
the completion will never be triggered.
On a system with high memory pressure, this can appear as the following
hung task:
INFO: task kworker/u385:17:8393 blocked for more than 122 seconds.
Tainted: G S E 6.19.0 #3
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u385:17 state:D stack:0 pid:8393 tgid:8393 ppid:2 task_flags:0x4248060 flags:0x00080000
Workqueue: xprtiod xprt_autoclose [sunrpc]
Call Trace:
<TASK>
__schedule+0x48b/0x18b0
? ib_post_send_mad+0x247/0xae0 [ib_core]
schedule+0x27/0xf0
schedule_timeout+0x104/0x110
__wait_for_common+0x98/0x180
? __pfx_schedule_timeout+0x10/0x10
wait_for_completion+0x24/0x40
rpcrdma_xprt_disconnect+0x444/0x460 [rpcrdma]
xprt_rdma_close+0x12/0x40 [rpcrdma]
xprt_autoclose+0x5f/0x120 [sunrpc]
process_one_work+0x191/0x3e0
worker_thread+0x2e3/0x420
? __pfx_worker_thread+0x10/0x10
kthread+0x10d/0x230
? __pfx_kthread+0x10/0x10
ret_from_fork+0x273/0x2b0
? __pfx_kthread+0x10/0x10
ret_from_fork_asm+0x1a/0x30
The Linux kernel CVE team has assigned CVE-2026-43469 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit 15788d1d1077ebe029c48842c738876516d85076 and fixed in 5.15.203 with commit 7ea69259a60a364f56cf4aa9e2eafb588d1c762b
Issue introduced in 5.13 with commit 15788d1d1077ebe029c48842c738876516d85076 and fixed in 6.1.167 with commit 8cb6b5d8296b1f99a8d36849901ebabfe3f749db
Issue introduced in 5.13 with commit 15788d1d1077ebe029c48842c738876516d85076 and fixed in 6.6.130 with commit 74c39a47856bddcde7874f2196a00143b5cd0af9
Issue introduced in 5.13 with commit 15788d1d1077ebe029c48842c738876516d85076 and fixed in 6.12.78 with commit 49f53ee4e25297d886f14e31f355ad1c2735ddfb
Issue introduced in 5.13 with commit 15788d1d1077ebe029c48842c738876516d85076 and fixed in 6.18.19 with commit 8127b5fec04757c2a41ed65bca0b3266968efd3b
Issue introduced in 5.13 with commit 15788d1d1077ebe029c48842c738876516d85076 and fixed in 6.19.9 with commit dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf
Issue introduced in 5.13 with commit 15788d1d1077ebe029c48842c738876516d85076 and fixed in 7.0 with commit 7b6275c80a0c81c5f8943272292dfe67730ce849
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-43469
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/sunrpc/xprtrdma/verbs.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/7ea69259a60a364f56cf4aa9e2eafb588d1c762b
https://git.kernel.org/stable/c/8cb6b5d8296b1f99a8d36849901ebabfe3f749db
https://git.kernel.org/stable/c/74c39a47856bddcde7874f2196a00143b5cd0af9
https://git.kernel.org/stable/c/49f53ee4e25297d886f14e31f355ad1c2735ddfb
https://git.kernel.org/stable/c/8127b5fec04757c2a41ed65bca0b3266968efd3b
https://git.kernel.org/stable/c/dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf
https://git.kernel.org/stable/c/7b6275c80a0c81c5f8943272292dfe67730ce849
reply other threads:[~2026-05-08 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050804-CVE-2026-43469-3846@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox