GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel nfsd: NFSv4 COMPOUND tag padding returns stale server memory bytes

UnscoredCVE-2026-99358Kernel, userspace & hypervisorcurated

Impact

The server does not zero the XDR padding after a COMPOUND tag in its reply. If a client sends a tag whose length is not a multiple of four, it gets back one to three stale bytes from the response page per reply. This is a small, repeatable leak of server memory. The record does not say what data can end up in those bytes. Severity is low next to the other nfsd fixes in this release.

Who can reach it

Any NFSv4 client that can send COMPOUND requests to the server.

What to do

Pick up the fix in the next scheduled kernel update for NFS servers; it takes effect after a reboot. On its own, this does not justify an emergency window.

References

Related entries

All Kernel, userspace & hypervisor 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.