rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.236.19.137.0In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial
In rxrpc_post_response(), the code should be comparing the challenge serial number from the cached response before deciding to switch to a newer response, but looks at the newer packet private data instead, rendering the comparison always false.
Fix this by switching to look at the older packet.
Fix further[1] to substitute the new packet in place of the old one if newer and also to release whichever we don't use.
From the CVE record · Linux
The Linux kernel's rxrpc code compares a challenge serial number from the wrong packet when deciding whether to replace a queued response. The input does not establish what an attacker can accomplish or whether exploitation requires network access, authentication, or user interaction.
Teams running Linux kernels with the affected rxrpc code should check their versions; the affected version range was not provided.