nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f · < 74ad36ed60df561a303a19ecef400c7096b20306| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()
Lei Lu recently reported that nfsd4_setclientid_confirm() did not check the return value from get_client_locked(). a SETCLIENTID_CONFIRM could race with a confirmed client expiring and fail to get a reference. That could later lead to a UAF.
Fix this by getting a reference early in the case where there is an extant confirmed client. If that fails then treat it as if there were no confirmed client found at all.
In the case where the unconfirmed client is expiring, just fail and return the result from get_client_locked().
From the CVE record · Linux
The Linux kernel’s nfsd4_setclientid_confirm() does not check whether get_client_locked() succeeds. A SETCLIENTID_CONFIRM request can race with a confirmed client expiring, potentially causing a use-after-free. The input does not specify authentication requirements or user interaction.
Engineers running the Linux kernel with nfsd should check their exposure; affected versions are not specified.