CVE-2026-90103NFSv4.2: fix LAYOUTSTATS send buffer exhaustion
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 18, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 27c430644369ccd9a2272492ba6d0e85e2e4800b before 842ac26615424577f24f0486b9d3bf97f28fad9c; from 27c430644369ccd9a2272492ba6d0e85e2e4800b before 397aa7000bbf6b6a0d32e66a544e978fb478c8e4; from 27c430644369ccd9a2272492ba6d0e85e2e4800b before e82d7d999fe9f893f84bf332fd39cb5d9de7128f; 27c430644369ccd9a2272492ba6d0e85e2e4800b builds before 5aca000630c0fd0da102ae1abf9245dd74f2ce36; from 27c430644369ccd9a2272492ba6d0e85e2e4800b before cb11590c7ddc6883a1b1d70b1f98b2779fe626f2; from 27c430644369ccd9a2272492ba6d0e85e2e4800b before 3815b894b922e9b4f40b8b6f6d67bf80d44141c9; from 27c430644369ccd9a2272492ba6d0e85e2e4800b before a973622da0c62c34043ddbbf382cd761b03e5136; from 27c430644369ccd9a2272492ba6d0e85e2e4800b before c75ef2137e749f2673f0617cfdaae53b2bb7195a | CNA record |
References
- https://git.kernel.org/stable/c/842ac26615424577f24f0486b9d3bf97f28fad9c
- https://git.kernel.org/stable/c/397aa7000bbf6b6a0d32e66a544e978fb478c8e4
- https://git.kernel.org/stable/c/e82d7d999fe9f893f84bf332fd39cb5d9de7128f
- https://git.kernel.org/stable/c/5aca000630c0fd0da102ae1abf9245dd74f2ce36
- https://git.kernel.org/stable/c/cb11590c7ddc6883a1b1d70b1f98b2779fe626f2
- https://git.kernel.org/stable/c/3815b894b922e9b4f40b8b6f6d67bf80d44141c9
- https://git.kernel.org/stable/c/a973622da0c62c34043ddbbf382cd761b03e5136
- https://git.kernel.org/stable/c/c75ef2137e749f2673f0617cfdaae53b2bb7195a
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.