xprtrdma: Decrement re_receiving on the early exit paths
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 15788d1d1077ebe029c48842c738876516d85076 · fixed in 7ea69259a60a364f56cf4aa9e2eafb588d1c762b; From 15788d1d1077ebe029c48842c738876516d85076 · fixed in 8cb6b5d8296b1f99a8d36849901ebabfe3f749db; From 15788d1d1077ebe029c48842c738876516d85076 · fixed in 74c39a47856bddcde7874f2196a00143b5cd0af9; From 15788d1d1077ebe029c48842c738876516d85076 · fixed in 49f53ee4e25297d886f14e31f355ad1c2735ddfb; From 15788d1d1077ebe029c48842c738876516d85076 · fixed in 8127b5fec04757c2a41ed65bca0b3266968efd3b; From 15788d1d1077ebe029c48842c738876516d85076 · fixed in dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf; From 15788d1d1077ebe029c48842c738876516d85076 · fixed in 7b6275c80a0c81c5f8943272292dfe67730ce849
- Linux Linux
5.13
- KernelLinux
From 5.13.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.167; From 6.2.0 · fixed in 6.6.130; From 6.7.0 · fixed in 6.12.78; From 6.13.0 · fixed in 6.18.19; From 6.19.0 · fixed in 6.19.9
References 7
git.kernel.org
- stable/c/7ea69259a60a364f56cf4aa9e2eafb588d1c762b
- stable/c/8cb6b5d8296b1f99a8d36849901ebabfe3f749db
- stable/c/74c39a47856bddcde7874f2196a00143b5cd0af9
- stable/c/49f53ee4e25297d886f14e31f355ad1c2735ddfb
- stable/c/8127b5fec04757c2a41ed65bca0b3266968efd3b
- stable/c/dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf
- stable/c/7b6275c80a0c81c5f8943272292dfe67730ce849