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.

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-31642
• https://git.kernel.org/stable/c/146d4ab94cf129ee06cd467cb5c71368a6b5bad6
• https://git.kernel.org/stable/c/3be718f659683ad89fad6f1eb66bee99727cae64
• https://git.kernel.org/stable/c/93fc15be44a35b8e3c58d0238ac0d9b7c53465ff
• https://git.kernel.org/stable/c/ac5f54691be06a32246179d41be2d73598036deb
• https://git.kernel.org/stable/c/c63abf25203b50243fe228090526f9dbf37727bd