nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo
Exact source revision recorded 24 Oct 2026 16:17:04 UTC. It does not establish the source's current position. Latest evidence.
cve-program · CVE-2026-89673
PublishedIn 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.
- Source published
- 11 Sep 2026 19:45:58 UTC
- Source modified
- 24 Oct 2026 14:15:11 UTC
- Observed here
- 24 Oct 2026 16:17:04 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.