nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel f9868174af49d207fbaf0c5e055d088a983684af, Kernel 0380129b1373c437eb35401a174671c8888f4b80, Kernel 29e4478e2ed5a227e8f0c33cacb91bf227cedd47 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget The XDR buffer size calculation in nfsd4_ff_encode_layoutget() has multiple errors that can result in either an out-of-bounds write or leaking uninitialized kernel memory to the client: - fh_len doesn't account for XDR padding on the file handle data - uid and gid lengths use "8 + len" but xdr_encode_opaque() actually writes "4 + xdr_align_size(len)" bytes - ds_len omits the flags and stats_collect_hint fields (8 bytes), while len's header constant overestimates by 8 bytes -- these partially cancel but leave a net mismatch The worst case occurs with short strings (e.g. uid=0, gid=0 with an odd-sized file handle), where the function writes up to 5 bytes past the reserved XDR buffer. Conversely, when string lengths happen to be 4-byte aligned, the reservation is too large and stale buffer content is sent to the client. Fix this by breaking out every encoded field explicitly in the ds_len calculation, using xdr_align_size() for all variable-length opaque fields, and correcting the header constants.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=9b9960a0ca4773e21c4b153ed355583946346b25 <f9868174af49d207fbaf0c5e055d088a983684af, >=9b9960a0ca4773e21c4b153ed355583946346b25 <0380129b1373c437eb35401a174671c8888f4b80, >=9b9960a0ca4773e21c4b153ed355583946346b25 <29e4478e2ed5a227e8f0c33cacb91bf227cedd47, >=9b9960a0ca4773e21c4b153ed355583946346b25 <3a7fd224df0fbb42167eb1b77be45d72fe0b1098, >=9b9960a0ca4773e21c4b153ed355583946346b25 <65a72b721943618eeb3a41c8b36e915591f3f83f, >=9b9960a0ca4773e21c4b153ed355583946346b25 <bee826c00ac900473f91306f1f3e5a5a81fd4a74, >=9b9960a0ca4773e21c4b153ed355583946346b25 <c81cef6a805dec266c10fc4f83c93d6fcf1a2b43, >=9b9960a0ca4773e21c4b153ed355583946346b25 <e7d9d23ecd9172f05b09bb678ff22db8e361c428, =4.8 | f9868174af49d207fbaf0c5e055d088a983684af, 0380129b1373c437eb35401a174671c8888f4b80, 29e4478e2ed5a227e8f0c33cacb91bf227cedd47, 3a7fd224df0fbb42167eb1b77be45d72fe0b1098, 65a72b721943618eeb3a41c8b36e915591f3f83f, bee826c00ac900473f91306f1f3e5a5a81fd4a74, c81cef6a805dec266c10fc4f83c93d6fcf1a2b43, e7d9d23ecd9172f05b09bb678ff22db8e361c428 |
| linux-kernel: Kernel | >=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.2.0 <6.6.157, >=6.7.0 <6.12.109, >=4.8.0 <5.10.270 | 5.15.221, 6.1.188, 6.18.50, 7.2.4, 6.6.157, 6.12.109, 5.10.270 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket