CVE-2025-68185
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.
Affected versions
Linux kernel versions
2.6.12
and later are affected. Fixed in
5.4.302,
5.10.247,
5.15.197,
6.1.159,
6.6.117,
6.12.58,
6.17.8,
6.18
and their respective stable series.
References
The following references provide additional information about CVE-2025-68185 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/40be5b9080114f18b0cea386db415b68a7273c1a
-
PatchKernel patch commithttps://git.kernel.org/stable/c/504b3fb9948a9e96ebbabdee0d33966a8bab15cb
-
PatchKernel patch commithttps://git.kernel.org/stable/c/6025f641a0e30afdc5aa62017397b1860ad9f677
Frequently asked questions
-
What is CVE-2025-68185?
CVE-2025-68185 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 2.6.12 onward and has been patched in 5.4.302, 5.10.247, 5.15.197 and others. CVE-2025-68185 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2025-68185?
Yes — CVE-2025-68185 has been patched. Fixed versions include 5.4.302, 5.10.247, 5.15.197 and others. If you are running Linux kernel 2.6.12 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-68185 actively exploited?
No — CVE-2025-68185 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.