Dismissed
(max. allowed matches exceeded)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo nfsd4_ff_encode_getdeviceinfo() computes the da_addr_body reservation as 16 + netid_len + addr_len, but the subsequent xdr_encode_opaque() calls emit 8 + round_up(netid_len, 4) + round_up(addr_len, 4) bytes. The mismatch means the declared da_addr_body length exceeds the actual encoded data by 2-8 bytes on every flexfile GETDEVICEINFO reply, leaking stale reply-page content to the client and mis-aligning the subsequent version list decode. Use xdr_align_size() for each string length to match what xdr_encode_opaque() actually writes.
References
Affected products
Linux
- <7.2.4
- <74015b7be806ad9e21d46f7bd2831df280c6c783
- <6.12.109
- <41ebca28e17f84293650598f86bd69532ec1a8e0
- <8b989aaec85e1293a871d602590c951fe44b8647
- <6.18.50
- <7.3-rc1
- <62e5949f0dd5ec837af144860ff908369df4c7c9