rxrpc: Fix memory leaks in rxkad_verify_response()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ec832bd06d6fdf08b0455ab7c2a7a9104e029638 · < 34f61a07e0cdefaecd3ec03bb5fb22215643678f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix memory leaks in rxkad_verify_response()
Fix rxkad_verify_response() to free the ticket and the server key under all circumstances by initialising the ticket pointer to NULL and then making all paths through the function after the first allocation has been done go through a single common epilogue that just releases everything - where all the releases skip on a NULL pointer.
From the CVE record · Linux
The Linux kernel's rxrpc rxkad_verify_response() can leak the ticket and server key on some paths. The input does not specify how an attacker could trigger the leak, or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with rxrpc should check their versions against the vendor advisory; affected versions are not specified in the input.