GPU VulnDB

Database/Control plane, storage & DevOps

libnfs: unvalidated string size causes an integer overflow when connecting to a crafted NFS server

CVSS 7.1CVE-2026-53689Control plane, storage & DevOpscurated

Impact

libnfs_zdr_string does not validate a string size, so a malicious or compromised NFS server can overflow an integer in a client that connects to it. The exposure is client-side: it matters where userspace NFS clients built on libnfs reach out to servers you do not fully control - QEMU's NFS block backend, backup and media tooling, utilities bundled into node images. It does not affect the in-kernel NFS client, and a fleet that only mounts its own storage over the kernel client is not exposed through this path. The record gives no exploitation detail beyond the integer overflow; CVSS rates confidentiality and integrity impact high with high attack complexity and required interaction.

Who can reach it

The client must connect to a server the attacker controls, so this needs either a hostile NFS endpoint or an on-path attacker plus whatever action triggers the connection. No authentication on the client side is involved.

What to do

Update libnfs past commit 55c18ea (releases through 6.0.2 are affected) and restart anything linked against it - for a distro package that means the usual package update plus restarting consumers such as QEMU processes, which for running VMs implies a live-migrate or a restart. Debian LTS has shipped an update. Meanwhile, restrict which NFS servers nodes are allowed to reach.

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.