LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68185: nfs4_setup_readdir(): insufficient locking for ->d_parent->d_inode dereferencing

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2025-68185 is a Linux kernel NFSv4 bug involving a race condition while preparing directory reads. The public record describes it as theoretically able to trigger a kernel oops, but difficult to hit on real hardware. No CVSS score, CWE, or active exploitation evidence is provided.

Executive priority

Treat this as routine kernel hygiene unless NFSv4 is business-critical or widely deployed. Patch through normal maintenance windows, with earlier action for virtualization-heavy environments or systems relying on untrusted NFSv4 mounts.

Technical view

The issue is insufficient locking in nfs4_setup_readdir() when dereferencing ->d_parent->d_inode. The fix moves xdr_encode_hyper()/put_unaligned_be64() under ->d_lock. The source characterizes impact as an oopsable race, with possible but difficult triggering under virtualized conditions.

Likely exposure

Exposure is most relevant to Linux systems using NFSv4 client functionality on affected kernel branches. The bundle lists Linux kernel versions and multiple stable-branch fixes, but does not provide distribution package names, CPEs, or a precise exploitability matrix.

Exploitation context

The CVE is not marked KEV, and the provided sources do not report active exploitation. The kernel description says exploitation is theoretical, likely hard on real hardware, and possibly more feasible on KVM, but still not easy to attack.

Researcher notes

Evidence is limited to the CVE record and kernel stable commits. The source names a locking defect and a narrow code fix, but does not establish reachable attack preconditions, privilege requirements, reproducibility, or confirmed denial-of-service impact.

Mitigation direction

  • Update to a vendor kernel containing the relevant stable-branch fix.
  • Check Linux distribution advisories for backported patches and fixed package versions.
  • Reduce or disable unnecessary NFSv4 client use until patched.
  • Prioritize hosts mounting untrusted or high-change NFSv4 shares.
  • Monitor vendor guidance because no standalone workaround is named.

Validation and detection

  • Inventory Linux kernel versions across systems using NFSv4.
  • Identify hosts with active NFSv4 mounts or NFS client dependencies.
  • Confirm vendor packages include one of the cited stable fixes or backports.
  • Review kernel logs for unexplained NFS-related oops events.
  • Track CVE updates for CVSS, distro advisories, or changed exploit status.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-68185 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 5.4.302, 5.10.247, 5.15.197, 6.1.159, 6.6.117, 6.12.58, 6.17.8, 6.18affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.