# CVE-2026-89665: linux: In the Linux kernel, the following vulnerability has been resolved: nfsd: reject out-of-range useconds in NFSv2 SETA... CVE-2026-89665 is fixed in 17 products on 1 platform, first by DEBIAN-CVE-2026-89665, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-89665 - Priority: High - CVSS: 8.2 (high) - EPSS: 0.0062 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Sep 11, 2026 ## Description 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 ] ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | dtb-aarch64 opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-64kb opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-64kb sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-64kb sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-azure opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-azure sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-azure sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-default opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-default sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-default sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24197-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24197-1.md) | Nov 7, 2026 | | Linux | kernel-default-base opensuse-leap 16.0 | 6.12.0-160000.39.1.160000.2.25 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-default-base sles 15.7 | 6.4.0-150700.53.84.1.150700.17.47.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-default-base sles 16.0 | 6.12.0-160000.39.1.160000.2.26 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-docs opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-docs sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-docs sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-kvmsmall opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-kvmsmall sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-livepatch-SLE15-SP7-RT_Update_21 sles 15.7 | 1-150700.1.3.1 | [SUSE-SU-2026:4640-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4640-1.md) | Nov 7, 2026 | | Linux | kernel-livepatch-SLE15-SP7_Update_22 sles 15.7 | 1-150700.15.3.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-obs-build opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-obs-build sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-obs-qa opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-obs-qa sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-rt opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-source opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-source sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-source sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-syms opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-syms sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-syms sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-zfcpdump opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-zfcpdump sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-zfcpdump sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | linux Debian 12.15 (bookworm) | 6.1.190-1 | [DEBIAN-CVE-2026-89665](https://patchblox.com/security/data/fix/linux/debian-cve-2026-89665.md) | Sep 23, 2026 | | Linux | linux Debian 13.5 (trixie) | 6.12.111-1 | [DEBIAN-CVE-2026-89665](https://patchblox.com/security/data/fix/linux/debian-cve-2026-89665.md) | Sep 23, 2026 | | Linux | linux Debian 14 | 7.2.6-1 | [DEBIAN-CVE-2026-89665](https://patchblox.com/security/data/fix/linux/debian-cve-2026-89665.md) | Sep 23, 2026 | | Linux | linux-6.12 Debian 12.15 (bookworm) | 6.12.111-1~deb12u1 | [DEBIAN-CVE-2026-89665](https://patchblox.com/security/data/fix/linux/debian-cve-2026-89665.md) | Sep 23, 2026 | --- Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.