nfsd: never defer requests during idmap lookup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2f425878b6a71571341dcd3f9e9d1a6f6355da9c · < d75ec4504a4340b033b15cad0303988b3089dd93| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfsd: never defer requests during idmap lookup
During v4 request compound arg decoding, some ops (e.g. SETATTR) can trigger idmap lookup upcalls. When those upcall responses get delayed beyond the allowed time limit, cache_check() will mark the request for deferral and cause it to be dropped.
This prevents nfs4svc_encode_compoundres from being executed, and thus the session slot flag NFSD4_SLOT_INUSE never gets cleared. Subsequent client requests will fail with NFSERR_JUKEBOX, given that the slot will be marked as in-use, making the SEQUENCE op fail.
Fix this by making sure that the RQ_USEDEFERRAL flag is always clear during nfs4svc_decode_compoundargs(), since no v4 request should ever be deferred.
From the CVE record · Linux
The Linux kernel’s nfsd can defer an NFSv4 request if an idmap lookup response is delayed beyond the allowed time limit. The session slot then remains in use, causing subsequent client requests to fail with NFSERR_JUKEBOX. This can occur during NFSv4 request decoding; the input does not specify authentication requirements.
Engineers running Linux kernel NFSv4 servers should check their kernel version against the vendor advisory; affected versions are not listed in the input.