LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid

In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid Fixes a crash when layout is null during this call stack: write_inode -> nfs4_write_inode -> pnfs_layoutcommit_inode pnfs_set_layoutcommit relies on the lseg refcount to keep the layout around. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt to reference a null layout.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash systems using NFSv4/pNFS when the kernel later references a layout that has become null. The public record describes reliability impact, not data theft or code execution. Severity and CVSS are not provided, so urgency depends on whether affected kernels use NFSv4/pNFS in production.

Executive priority

Treat as a targeted stability risk for Linux NFS users. Prioritize patch planning where NFSv4/pNFS supports critical services; otherwise track in normal kernel maintenance until vendor severity is clarified.

Technical view

The fix clears NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid. Without that, write_inode through nfs4_write_inode to pnfs_layoutcommit_inode can attempt layoutcommit processing after layout state is invalid, causing a null layout reference and crash.

Likely exposure

Likely exposure is Linux systems running affected kernel versions with NFSv4/pNFS client paths in use. The source lists Linux as affected and includes multiple stable-kernel fix commits. Exact distribution package exposure requires vendor or distro mapping.

Exploitation context

No KEV listing is indicated, and the supplied sources do not report active exploitation or a public exploit. The evidence supports a kernel crash condition in a specific NFSv4/pNFS path, not confirmed remote exploitation.

Researcher notes

The public record lacks CVSS, CWE, exploit status, and detailed affected distribution packages. Analysis should stay tied to kernel commit presence and NFSv4/pNFS usage rather than broad Linux exposure assumptions.

Mitigation direction

  • Apply Linux kernel updates that include the referenced stable fixes.
  • Use distribution kernel advisories to map package versions to fixed commits.
  • Prioritize servers or appliances using NFSv4/pNFS in production.
  • Review Siemens guidance if using affected Siemens-managed products.
  • If updates are unavailable, follow vendor-supported mitigations only.

Validation and detection

  • Inventory Linux kernel versions across NFS client systems.
  • Identify systems using NFSv4 and pNFS functionality.
  • Check whether deployed kernels include one referenced stable fix commit.
  • Review vendor advisories for distribution-specific fixed package versions.
  • Monitor for kernel crash reports involving pnfs_layoutcommit_inode or nfs4_write_inode.
Prepared
Confidence
medium
Sources
11

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-68349 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
2ADP providers
10Source 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
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fe1cf9469d7bcb6af27e42eb555a41b0135bce4aunaffected
LinuxLinux4.10, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2, 6.19affected
Weakness

CWE details

No CWE listed

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