In the Linux kernel, the following vulnerability has been resolved: rxrpc: only handle RESPONSE during service challenge Only process RESPONSE packets while the service connection is still in RXRPC_CONN_SERVICE_CHALLENGING. Check that state under state_lock before running response verification and security initialization, then use a local secured flag to decide whether to queue the secured-connection work after the state transition. This keeps duplicate or late RESPONSE packets from re-running the setup path and removes the unlocked post-transition state test.
https://git.kernel.org/stable/c/d0035e634dae83237ab7f5681eb52b2f65d0ceb8
https://git.kernel.org/stable/c/c43ffdcfdbb5567b1f143556df8a04b4eeea041c
https://git.kernel.org/stable/c/03fd2ef73cb4ffd0af100a95b634af54f474414e