CVE-2026-53392

NFSv4/flexfiles: reject zero filehandle version count

HIGH
7.5
CVSS Score
Published: July 19, 2026 at 12:01 PM UTC
Updated: October 19, 2026 at 08:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: NFSv4/flexfiles: reject zero filehandle version count ff_layout_alloc_lseg() decodes the filehandle-version array count from the flexfiles layout body. The value is used as the count for kzalloc_objs(), and the current code only rejects NULL. A zero count yields ZERO_SIZE_PTR, which can be stored in dss_info->fh_versions even though later flexfiles paths assume that at least one filehandle version exists. Reject fh_count == 0 before the allocation, matching the existing zero version_count validation in the flexfiles GETDEVICEINFO parser. A QEMU/KASAN run with a malformed flexfiles layout hit: KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] RIP: 0010:ff_layout_encode_ff_layoutupdate.isra.0+0x15f/0x750 ff_layout_encode_layoutreturn+0x683/0x970 nfs4_xdr_enc_layoutreturn+0x278/0x3a0 Kernel panic - not syncing: Fatal exception The patched kernel rejects the malformed layout without KASAN/oops/panic, and a valid fh_count=1 regression still opens, reads, and unmounts cleanly.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.0 ≤ v < 5.10.2615.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.386.19 ≤ v < 7.1.36.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.964.0d67ae825a59d639e4d8b82413af84d854617a87e
Vendor states this is fixed in 18cc6d57a14fa65ab2a2b52279f549041c4bc9cf (fixed)
Vendor states this is fixed in 2131ed64b767ffa8bcdb3677d90f3964e39aabc8 (fixed)
Vendor states this is fixed in 2c6bb3c40bc24f6aa8dfbe6fe98c3ad6389203f2 (fixed)
Vendor states this is fixed in 7779c85028a0676fb190cde4f0c540f4f8e97761 (fixed)
Vendor states this is fixed in 9033591535c066726f5b505126ccb4068b98fa4f (fixed)
Vendor states this is fixed in be7829715e341b42846437dd9e721005db59f0cc (fixed)
Vendor states this is fixed in d8c90c7cc061265d5f2813a1f5c82ef2f4707e67 (fixed)
Vendor states this is fixed in eeabb9020721db6bc132e68eeae380b8d4fb4b04 (fixed)
Vendor states this is fixed in 4.0 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.38 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.3 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card