GPU VulnDB

Database/Control plane, storage & DevOps

Linux nfsd: flexfiles GETDEVICEINFO over-reserves da_addr_body and leaks reply-page memory

UnscoredCVE-2026-89673Control plane, storage & DevOpscurated

Impact

nfsd4_ff_encode_getdeviceinfo() declares a da_addr_body length of 16 + netid_len + addr_len while the xdr_encode_opaque() calls emit the 4-byte-aligned form, so the declared length exceeds the encoded data by 2 to 8 bytes on every flexfile GETDEVICEINFO reply. The surplus is stale reply-page content sent to the client, and it mis-aligns the client's decode of the version list that follows. This is a small but repeatable kernel memory disclosure from the shared storage server to any client that can ask for device info, and it only affects servers exporting pNFS flexfiles layouts.

Who can reach it

Any client that can mount the export and issue NFSv4.1+ GETDEVICEINFO for a flexfiles layout, under normal export authentication.

What to do

Upgrade to a stable kernel with the referenced commits and reboot the NFS server after draining clients. Not exploitable on servers that do not export pNFS flexfiles layouts. No fixed version numbers are stated in the record.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.