nfsd: check client ownership when cancelling a copy-notify stateid
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ce0887ac96d35c7105090e166bb0807dc0a0e838 · < b42dc26a14b4ad5d6daaada11ec4c70744141c25| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfsd: check client ownership when cancelling a copy-notify stateid
On the OFFLOAD_CANCEL path (clp != NULL), manage_cpntf_state() freed the target cpntf state without checking ownership. The lookup key st->si_opaque.so_id is allocated cyclically (guessable) and the embedded clientid is the fixed per-net nn->s2s_cp_cl_id, so any authenticated NFSv4.2 client could cancel and free another client's copy-notify stateid.
Compare the creating clientid recorded in state->cp_p_clid against the requesting client's cl_clientid and return nfserr_bad_stateid on a mismatch instead of freeing the entry.
From the CVE record · Linux
The Linux kernel’s nfsd OFFLOAD_CANCEL path did not verify ownership before freeing a copy-notify stateid. An authenticated NFSv4.2 client could cancel another client’s copy-notify stateid; no other user interaction is described.
Operators running the Linux kernel with NFSv4.2 server support should check their versions; affected versions are not specified.