nfs4_setup_readdir(): insufficient locking for ->d_parent->d_inode dereferencing
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 40be5b9080114f18b0cea386db415b68a7273c1a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfs4_setup_readdir(): insufficient locking for ->d_parent->d_inode dereferencing
Theoretically it's an oopsable race, but I don't believe one can manage to hit it on real hardware; might become doable on a KVM, but it still won't be easy to attack.
Anyway, it's easy to deal with - since xdr_encode_hyper() is just a call of put_unaligned_be64(), we can put that under ->d_lock and be done with that.
From the CVE record · Linux
The Linux kernel's nfs4_setup_readdir() insufficiently locks a dereference of a parent dentry's inode. The resulting race could theoretically cause a kernel oops, though the report says it may be impractical to trigger on real hardware. The input does not establish whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with the affected NFSv4 code should check their versions against the vendor advisory; affected versions are not specified.