NFSv4.2: fix LAYOUTSTATS send buffer exhaustion
Summary
| CVE | CVE-2026-90103 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-09-17 17:17:02 UTC |
|---|
| Updated | 2026-09-17 17:17:02 UTC |
|---|
| Description | In the Linux kernel, the following vulnerability has been resolved:
NFSv4.2: fix LAYOUTSTATS send buffer exhaustion
encode_layoutstats_maxsz budgets XDR_QUADLEN(PNFS_LAYOUTSTATS_MAXSIZE),
i.e. 256 bytes, for the layoutupdate4 body written by the layout driver.
The flexfiles record can exceed that.
ff_layout_encode_ff_layoutupdate() emits, per data server, a netaddr4,
an nfs_fh4, two ff_io_latency4, an nfstime4 and a bool. A data server
whose filehandle is NFS_MAXFHSIZE bytes long already accounts for 132 of
those bytes, and the two ff_io_latency4 at 64 bytes each, the nfstime4
and the bool add a further 144, so the body passes 256 bytes before the
netaddr4 is encoded at all. encode_layoutstats() additionally writes
the deviceid4 and the layoutupdate4 lou_type word, neither of which the
macro accounts for.
The filehandle and the address are both chosen by the server, through
LAYOUTGET and GETDEVICEINFO, so it can drive the encoder past the
end of the send buffer. xdr_reserve_space() returns NULL once that
happens, and the two ff_layout_encode_io_latency() calls run with
dss_info->mirror->lock held, so a NULL return there leaves the lock
permanently held.
Raise PNFS_LAYOUTSTATS_MAXSIZE to 384 so that the record fits inside the
reservation. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 27c430644369ccd9a2272492ba6d0e85e2e4800b 842ac26615424577f24f0486b9d3bf97f28fad9c git |
Not specified |
| CNA |
Linux |
Linux |
affected 27c430644369ccd9a2272492ba6d0e85e2e4800b 397aa7000bbf6b6a0d32e66a544e978fb478c8e4 git |
Not specified |
| CNA |
Linux |
Linux |
affected 27c430644369ccd9a2272492ba6d0e85e2e4800b e82d7d999fe9f893f84bf332fd39cb5d9de7128f git |
Not specified |
| CNA |
Linux |
Linux |
affected 27c430644369ccd9a2272492ba6d0e85e2e4800b 5aca000630c0fd0da102ae1abf9245dd74f2ce36 git |
Not specified |
| CNA |
Linux |
Linux |
affected 27c430644369ccd9a2272492ba6d0e85e2e4800b cb11590c7ddc6883a1b1d70b1f98b2779fe626f2 git |
Not specified |
| CNA |
Linux |
Linux |
affected 27c430644369ccd9a2272492ba6d0e85e2e4800b 3815b894b922e9b4f40b8b6f6d67bf80d44141c9 git |
Not specified |
| CNA |
Linux |
Linux |
affected 27c430644369ccd9a2272492ba6d0e85e2e4800b a973622da0c62c34043ddbbf382cd761b03e5136 git |
Not specified |
| CNA |
Linux |
Linux |
affected 27c430644369ccd9a2272492ba6d0e85e2e4800b c75ef2137e749f2673f0617cfdaae53b2bb7195a git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.2 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.2 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.270 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.221 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/5aca000630c0fd0da102ae1abf9245dd74f2ce36 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a973622da0c62c34043ddbbf382cd761b03e5136 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/842ac26615424577f24f0486b9d3bf97f28fad9c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/397aa7000bbf6b6a0d32e66a544e978fb478c8e4 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e82d7d999fe9f893f84bf332fd39cb5d9de7128f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3815b894b922e9b4f40b8b6f6d67bf80d44141c9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/cb11590c7ddc6883a1b1d70b1f98b2779fe626f2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c75ef2137e749f2673f0617cfdaae53b2bb7195a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.