nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()
dentry_create() can hypothetically provide a different dentry than the one passed in. This could happen, for example, if the exported filesystem is NFS, and the server returned to OPEN a filehandle which matched a directory that was already in the dcache. Clearly this would not be expected!
If this were to happen the dentry (child) that was already stored in resfhp could be freed and later dereferenced.
We shouldn't call fh_compose() until we are certain that we have the final dentry, so this patch moved the fh_compose() call to two places: one for the case where the target already exists, and one after dentry_create() where it was created.
From the CVE record · Linux
The Linux kernel’s NFS server code can compose a filehandle using the wrong dentry if dentry_create() returns a different dentry than expected. In that case, a previously stored dentry could be freed and later dereferenced. This could occur when the exported filesystem is NFS and the server returns an OPEN filehandle matching a directory already in the dcache; the input does not establish attacker access requirements or a specific exploit outcome.
Engineers running the Linux kernel’s NFS server should check their systems; affected versions are not specified.