Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 084bebe82ad86f718a3af84f34761863e63164ed, 104080582ae0aa6dce6c6d75ff89062efe84673b, 38694f9aae00459ab443a7dc8b3949a6b33b560a; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 084bebe82ad86f718a3af84f34761863e63164ed, 104080582ae0aa6dce6c6d75ff89062efe84673b, 38694f9aae00459ab443a7dc8b3949a6b33b560a; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Dec 24, 2025
Updated
Nov 10, 2026
EPSS
0.7% · 53th percentile
CWE
—

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68349

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.10affected
    • fe1cf9469d7bcb6af27e42eb555a41b0135bce4a and later · before 084bebe82ad86f718a3af84f34761863e63164edaffected · git
    • fe1cf9469d7bcb6af27e42eb555a41b0135bce4a and later · before b6e4e3a08c03200cc4b8067ec8ab3172a989d6fcaffected · git
    • fe1cf9469d7bcb6af27e42eb555a41b0135bce4a and later · before 104080582ae0aa6dce6c6d75ff89062efe84673baffected · git
    • fe1cf9469d7bcb6af27e42eb555a41b0135bce4a and later · before f718f9ea6094843b8c059b073af49ad61e9f49bbaffected · git
    • fe1cf9469d7bcb6af27e42eb555a41b0135bce4a and later · before 59947dff0fb7c19c09ce6dccbcd253fd542b6c25affected · git
    • fe1cf9469d7bcb6af27e42eb555a41b0135bce4a and later · before ca2e7fdad7c683b64821c94a58b9b68733214dadaffected · git
    • fe1cf9469d7bcb6af27e42eb555a41b0135bce4a and later · before 38694f9aae00459ab443a7dc8b3949a6b33b560aaffected · git
    • fe1cf9469d7bcb6af27e42eb555a41b0135bce4a and later · before e0f8058f2cb56de0b7572f51cd563ca5debce746affected · git
    • before 4.10not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.38.1.el10_16.12.0-124.38.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.38.1.el10_16.12.0-124.38.1.el10_1
AlmaLinux:8bpftoolbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.104.1.el8_104.18.0-553.104.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.104.1.rt7.445.el8_104.18.0-553.104.1.rt7.445.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.104.1.rt7.445.el8_104.18.0-553.104.1.rt7.445.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.104.1.rt7.445.el8_104.18.0-553.104.1.rt7.445.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.104.1.rt7.445.el8_104.18.0-553.104.1.rt7.445.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.104.1.rt7.445.el8_104.18.0-553.104.1.rt7.445.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.104.1.rt7.445.el8_104.18.0-553.104.1.rt7.445.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.104.1.rt7.445.el8_104.18.0-553.104.1.rt7.445.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68347Dec 24, 2025 · ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events
    31Monitor
  • ← EarlierCVE-2025-68348Dec 24, 2025 · block: fix memory leak in __blkdev_issue_zero_pages
    0Monitor
  • Later →CVE-2025-68350Dec 24, 2025 · exfat: fix divide-by-zero in exfat_allocate_bitmap
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux084bebe82ad86f718a3af84f34761863e63164edVendor (CNA)
Linux Linux104080582ae0aa6dce6c6d75ff89062efe84673bVendor (CNA)
Linux Linux38694f9aae00459ab443a7dc8b3949a6b33b560aVendor (CNA)
Linux Linux59947dff0fb7c19c09ce6dccbcd253fd542b6c25Vendor (CNA)
Linux Linuxb6e4e3a08c03200cc4b8067ec8ab3172a989d6fcVendor (CNA)
Linux Linuxca2e7fdad7c683b64821c94a58b9b68733214dadVendor (CNA)
Linux Linuxe0f8058f2cb56de0b7572f51cd563ca5debce746Vendor (CNA)
Linux Linuxf718f9ea6094843b8c059b073af49ad61e9f49bbVendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.104.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
opensuse:kernel-source6.18.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:bpftool0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+6

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records