CVE-2026-31642
rxrpc: Fix call removal to use RCU safe deletion
Vexday Risk Score
3Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS —EPSS 0.1%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
24 Apr 2026Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix call removal to use RCU safe deletion
Fix rxrpc call removal from the rxnet->calls list to use list_del_rcu()
rather than list_del_init() to prevent stuffing up reading
/proc/net/rxrpc/calls from potentially getting into an infinite loop.
This, however, means that list_empty() no longer works on an entry that's
been deleted from the list, making it harder to detect prior deletion. Fix
this by:
Firstly, make rxrpc_destroy_all_calls() only dump the first ten calls that
are unexpectedly still on the list. Limiting the number of steps means
there's no need to call cond_resched() or to remove calls from the list
here, thereby eliminating the need for rxrpc_put_call() to check for that.
rxrpc_put_call() can then be fixed to unconditionally delete the call from
the list as it is the only place that the deletion occurs.
Affected products
Linux · LinuxWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://git.kernel.org/stable/c/146d4ab94cf129ee06cd467cb5c71368a6b5bad6https://git.kernel.org/stable/c/280efb85e9759881a9d31d0874baa04583cb6c09https://git.kernel.org/stable/c/3be718f659683ad89fad6f1eb66bee99727cae64https://git.kernel.org/stable/c/3e47a38e584b905359fe0ce5be5165d1e8592a90https://git.kernel.org/stable/c/93fc15be44a35b8e3c58d0238ac0d9b7c53465ffhttps://git.kernel.org/stable/c/ac5f54691be06a32246179d41be2d73598036debhttps://git.kernel.org/stable/c/b15b1ce96777b88989a6a4de8d01efbcd81ad2d7https://git.kernel.org/stable/c/c63abf25203b50243fe228090526f9dbf37727bd