nfsd: fix possible badness in FREE_STATEID
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.11.46.12In the Linux kernel, the following vulnerability has been resolved:
nfsd: fix possible badness in FREE_STATEID
When multiple FREE_STATEIDs are sent for the same delegation stateid, it can lead to a possible either use-after-free or counter refcount underflow errors.
In nfsd4_free_stateid() under the client lock we find a delegation stateid, however the code drops the lock before calling nfs4_put_stid(), that allows another FREE_STATE to find the stateid again. The first one will proceed to then free the stateid which leads to either use-after-free or decrementing already zeroed counter.
From the CVE record · Linux
The Linux kernel's nfsd can mishandle multiple FREE_STATEID requests for the same delegation stateid. A race between the requests can cause a use-after-free or a reference-count underflow. The input does not specify authentication or user-interaction requirements.
Operators running the Linux kernel should check whether their kernel includes the nfsd fix; affected versions are not specified.