CVE-2026-31642

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.

CVSS 3.1

5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

0.1% chance of exploitation in the next 30 days; higher than 2% of CVEs (scores of 2026-10-25)

CWE

CWE-835

Published

2026-04-24

Modified

2026-10-15

Record from

the NVD, synced 2026-10-19

Affected

• linux:linux_kernel

References

• https://git.kernel.org/stable/c/146d4ab94cf129ee06cd467cb5c71368a6b5bad6
• https://git.kernel.org/stable/c/280efb85e9759881a9d31d0874baa04583cb6c09
• https://git.kernel.org/stable/c/3be718f659683ad89fad6f1eb66bee99727cae64
• https://git.kernel.org/stable/c/3e47a38e584b905359fe0ce5be5165d1e8592a90
• https://git.kernel.org/stable/c/93fc15be44a35b8e3c58d0238ac0d9b7c53465ff

Check your stackJSON