afs: Fix the setting of the server responding flag
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.10.146.11.36.12In the Linux kernel, the following vulnerability has been resolved:
afs: Fix the setting of the server responding flag
In afs_wait_for_operation(), we set transcribe the call responded flag to the server record that we used after doing the fileserver iteration loop - but it's possible to exit the loop having had a response from the server that we've discarded (e.g. it returned an abort or we started receiving data, but the call didn't complete).
This means that op->server might be NULL, but we don't check that before attempting to set the server flag.
From the CVE record · Linux
The Linux kernel's AFS code may dereference a null server pointer when an operation exits the fileserver iteration loop after discarding a server response. The input does not specify how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Operators running Linux kernels with the affected AFS code should check their kernel version; affected versions are not specified.