rxrpc: only handle RESPONSE during service challenge
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 17926a79320afa9b95df6b977b40cca6d8713cea · < d0035e634dae83237ab7f5681eb52b2f65d0ceb8| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s rxrpc service-connection setup can process duplicate or late RESPONSE packets after the service challenge. An attacker able to send those packets could cause response verification and security initialization to run again. The input does not specify authentication or user-interaction requirements.
Teams running the Linux kernel should check their exposure; affected versions are not specified.