Skip to main content
VulnerabilityPublished Updated

CVE-2026-43469: Linux kernel · xprtrdma: Decrement re_receiving on the early exit paths

Source GCVE Database

0
Authoritative record:CVE-2026-43469· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf : patch Linux kernel soon.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf, 8127b5fec04757c2a41ed65bca0b3266968efd3b, 74c39a47856bddcde7874f2196a00143b5cd0af9 +4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 15788d1d1077ebe029c48842c738876516d85076, < dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf
Fixed in
  • dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf
LinuxLinuxAffected
  • ≥ 15788d1d1077ebe029c48842c738876516d85076, < 8127b5fec04757c2a41ed65bca0b3266968efd3b
Fixed in
  • 8127b5fec04757c2a41ed65bca0b3266968efd3b
LinuxLinuxAffected
  • ≥ 15788d1d1077ebe029c48842c738876516d85076, < 74c39a47856bddcde7874f2196a00143b5cd0af9
Fixed in
  • 74c39a47856bddcde7874f2196a00143b5cd0af9
LinuxLinuxAffected
  • ≥ 15788d1d1077ebe029c48842c738876516d85076, < 49f53ee4e25297d886f14e31f355ad1c2735ddfb
Fixed in
  • 49f53ee4e25297d886f14e31f355ad1c2735ddfb
LinuxLinuxAffected
  • ≥ 15788d1d1077ebe029c48842c738876516d85076, < 8cb6b5d8296b1f99a8d36849901ebabfe3f749db
Fixed in
  • 8cb6b5d8296b1f99a8d36849901ebabfe3f749db
LinuxLinuxAffected
  • ≥ 15788d1d1077ebe029c48842c738876516d85076, < 7ea69259a60a364f56cf4aa9e2eafb588d1c762b
Fixed in
  • 7ea69259a60a364f56cf4aa9e2eafb588d1c762b

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

References

Community reviews

Loading reviews…