CVE-2026-89673

nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo

N/A
Published: September 11, 2026 at 07:45 PM UTC
Updated: October 24, 2026 at 03:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

16282aeca44bfac0d1ac3be6cd1a719d6ff3d74919a648a07572c70fbe16faf0fafaf3dce9fd998a3f1a2b0b2d575f39ff0bedb5411822fe7446a8054.14.3264.19.2955.10.1955.15.1325.4.2576.1.536.4.166.5.36.66370e66a71c4869247f8f406c2a8b2c43df8998f6372e2ee629894433fe6107d7048536a3280a28464c959d59c24c661bd5338e4e6f1f703d7c309a16d08bd22fa2941a4d5ef45ed115dd00e484a93d782e36f0c287769a0430268739a71dbd56df0e679efcae97fa425ca6db9d126e37daccf2d7225cb09
Vendor states this is fixed in 41ebca28e17f84293650598f86bd69532ec1a8e0 (fixed)
Vendor states this is fixed in 62e5949f0dd5ec837af144860ff908369df4c7c9 (fixed)
Vendor states this is fixed in 74015b7be806ad9e21d46f7bd2831df280c6c783 (fixed)
Vendor states this is fixed in 88bce7e326c368d7df15126ccac537e54bebd467 (fixed)
Vendor states this is fixed in 8b989aaec85e1293a871d602590c951fe44b8647 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Affected range stops below 6.12.109, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.109 (unaffected)
Affected range stops below 6.18.50, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.18.50 (unaffected)
Affected range stops below 6.6.157, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.157 (unaffected)
Affected range stops below 7.2.4, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Affected range stops below 7.3-rc1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card