CVE-2025-68185
nfs4_setup_readdir(): insufficient locking for ->d_parent->d_inode dereferencing
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.12
References 8
git.kernel.org
- stable/c/6025f641a0e30afdc5aa62017397b1860ad9f677
- stable/c/e6cafe71eb3b5579b245ba1bd528a181e77f3df1
- stable/c/fa4daf7d11e45b72aad5d943a7ab991f869fff79
- stable/c/504b3fb9948a9e96ebbabdee0d33966a8bab15cb
- stable/c/eacfd08b26a062f1095b18719715bc82ad35312e
- stable/c/40be5b9080114f18b0cea386db415b68a7273c1a
- stable/c/f5e570eaab36a110c6ffda32b87c51170990c2d1
- stable/c/a890a2e339b929dbd843328f9a92a1625404fe63