nfsd: fix possible fh_compose of wrong dentry in nfsd4_create_file()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 033e783709ce99662cf81f6abcad746a8da9d35f and Kernel 3e2c79360c6a89975ec5b5a7d4ef937e4db91a27.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=64a989dbd144e0622371396461b11335459692d2 <033e783709ce99662cf81f6abcad746a8da9d35f, >=64a989dbd144e0622371396461b11335459692d2 <3e2c79360c6a89975ec5b5a7d4ef937e4db91a27 | 033e783709ce99662cf81f6abcad746a8da9d35f, 3e2c79360c6a89975ec5b5a7d4ef937e4db91a27 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket