Bug 2532322 (CVE-2026-89673) - CVE-2026-89673 kernel: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo
Summary: CVE-2026-89673 kernel: nfsd: fix XDR padding calculation in ff_encode_getdevi...
Keywords:
Status: NEW
Alias: CVE-2026-89673
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-11 22:21 UTC by OSIDB Bzimport
Modified: 2026-09-16 10:23 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-11 22:21:19 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.