CVE-2026-89665: Linux kernel · nfsd: reject out-of-range useconds in NFSv2 SETATTR/CREATE

In the Linux kernel, the following vulnerability has been resolved: nfsd: reject out-of-range useconds in NFSv2 SETATTR/CREATE The NFSv2 sattr decoder converts the wire useconds to nanoseconds in svcxdr_decode_sattr(): iap->ia_atime.tv_nsec = tmp2 * NSEC_PER_USEC; tmp2 is a u32 and NSEC_PER_USEC is 1000, so the product is computed in unsigned long. On ILP32 that is 32 bits, and an out-of-range useconds value such as 4294968 wraps to tv_nsec == 704. The corruption therefore happens during decode, before any proc function can inspect the value, and a later range check on tv_nsec would see an in-range result and accept it. Rejecting in the decoder yields an RPC GARBAGE_ARGS reply. NFSv2 defines no NFSERR_INVAL, so there is no NFS-level status to return for a malformed time argument, and the check cannot move to the proc function the way the v3/v4 nsec range checks do. Guard the raw useconds before the multiplication and reject values greater than 1000000. useconds == 1000000 is kept: it is the Sun convention for "set to the current server time", and the in-tree Linux NFSv2 client emits it in both the atime and the mtime field for a plain touch / utimes(file, NULL) (see encode_sattr() and xdr_encode_current_server_time() in fs/nfs/nfs2xdr.c). Rejecting 1000000 would turn that common operation into a hard decode failure for both SETATTR and CREATE. 1000000 * NSEC_PER_USEC is 10^9, which does not wrap on ILP32, so the Sun convention value passes through safely. Only genuinely out-of-range values (> 1000000) are rejected. The atime and mtime guards are therefore symmetric. The decoder only applied the Sun convention in the mtime block, which clears ATTR_ATIME_SET|ATTR_MTIME_SET when mtime useconds == 1000000. If a client puts 1000000 in the atime field but not in the mtime field, the atime block stored an out-of-range tv_nsec (10^9) and left ATTR_ATIME_SET set, so the bogus value reached the filesystem. Apply the convention in the atime block as well, clearing ATTR_ATIME_SET so the server uses its current time and ignores the value. Only ATTR_ATIME_SET is cleared there. The mtime block keeps its existing behavior, where 1000000 means "set both atime and mtime to now". [ cel: various tweaks, addenda, and clean-ups ]

• ubuntu.com/security/CVE-2026-89665 (opens in a new tab)
• cve.org/CVERecord?id=CVE-2026-89665 (opens in a new tab)
• git.kernel.org/linus/26709c8ffe73772eb69e68d553ac71d91228dccc (opens in a new tab)
• git.kernel.org/stable/c/1195483965a5f63d2dde18054ec7e50a23b9071c (opens in a new tab)
• git.kernel.org/stable/c/26709c8ffe73772eb69e68d553ac71d91228dccc (opens in a new tab)
• git.kernel.org/stable/c/a937dd1aa2d92291fe0a1860d17e90d8f206cd22 (opens in a new tab)
• git.kernel.org/stable/c/ad02d095439f89cbd6629420c7e3ba476457b83b (opens in a new tab)

• CVE-2026-99999: Linux kernel · ipv4: validate checksum_start before completing checksumCriticalVulnerability2026-10-15
• CVE-2026-99083: Linux kernel · ksmbd: fix heap out-of-bounds write in krb5_authenticate()HighVulnerability2026-10-26
• CVE-2026-99080: Linux kernel · fs: Free any excess xarray nodes in clear_inode()MediumVulnerability2026-10-26
• CVE-2026-99077: Linux kernel · ipv4: udp: Create exceptions before socket matchingHighVulnerability2026-10-26
• CVE-2026-99067: Linux kernel · btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode()MediumVulnerability2026-10-26