nfsd: clear XDR padding in GETXATTR replies
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel daba58690339ae86f1ebeb5197aa1369fae37e57, Kernel 624531ecd48b96be2a94c964685762960bd11208, Kernel 842e2215a87d062b69d5170840f34fbd83f47b41 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: nfsd: clear XDR padding in GETXATTR replies nfsd4_vbuf_to_stream() uses a raw memcpy() for the first fragment of an attribute value. xdr_reserve_space() aligns the reservation but does not initialize the extra bytes. If the complete value fits in that fragment, the loop that clears padding for the final fragment is never entered. A remote client reading an attribute whose length is not a multiple of four can therefore receive one to three stale bytes from the response page. Encode the first fragment with xdr_encode_opaque_fixed(), matching the final-fragment path and ensuring that any XDR padding is zeroed.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=23e50fe3a5e6045a573c69d4b0e3d78aa6183323 <daba58690339ae86f1ebeb5197aa1369fae37e57, >=23e50fe3a5e6045a573c69d4b0e3d78aa6183323 <624531ecd48b96be2a94c964685762960bd11208, >=23e50fe3a5e6045a573c69d4b0e3d78aa6183323 <842e2215a87d062b69d5170840f34fbd83f47b41, >=23e50fe3a5e6045a573c69d4b0e3d78aa6183323 <99ab5346b69834587b4ae59d1addea5960b50c8b, =5.9 | daba58690339ae86f1ebeb5197aa1369fae37e57, 624531ecd48b96be2a94c964685762960bd11208, 842e2215a87d062b69d5170840f34fbd83f47b41, 99ab5346b69834587b4ae59d1addea5960b50c8b |
| linux-kernel: Kernel | >=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=5.9.0 <6.12.117 | 6.18.61, 7.3.2, 6.12.117 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket