CVE-2026-89666— Linux NFS服务端越界nseconds拒绝漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已修复以下漏洞： nfsd：拒绝 NFSv3 SETATTR 和创建操作中超范围的 nseconds 客户端可以发送携带 或 的 NFSv3 SETATTR、CREATE、MKDIR、SYMLINK 或 MKNOD 请求，其中 字段超出有效范围。该值在传输层格式正确，能干净地解码为有效的 ，但其数值不是合法的 ： 必须小于 。 在 setattr 路径中，没有任何地方对该值进行限幅（clamping）。 会将时间值通过 处理；当文件系统支持纳秒粒度（ ）时，该函数不会将 缩小到小于 。此外，
影响版本矩阵 10
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 55341d8a5a0f5853e70d46f5a55cf06007808f1d |
affected |
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 54e02f5e32c52fb395f2ee02986a6c6d5608d22b |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< e2543852152bcf9aeb57da17d9f9219f7df8aafb |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< eb0eca7720662ba5847df1510e73801f7f473094 |
affected | ||
2.6.12 |
affected | ||
< 2.6.12 |
unaffected | ||
6.12.109≤ 6.12.* |
unaffected | ||
6.18.50≤ 6.18.* |
unaffected | ||
| … +2 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-89666 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
nfsd: reject out-of-range nseconds in NFSv3 SETATTR and create ops
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
nfsd: reject out-of-range nseconds in NFSv3 SETATTR and create ops
A client can send an NFSv3 SETATTR, CREATE, MKDIR, SYMLINK or MKNOD
carrying an atime or mtime whose nseconds field is out of range. The
value is well-formed on the wire and decodes cleanly into a valid
uint32, but it is not a valid timespec64: tv_nsec must be less than
NSEC_PER_SEC.
Nothing in the setattr path clamps it. notify_change() runs the time
through timestamp_truncate(), which does not reduce tv_nsec below
NSEC_PER_SEC when the filesystem supports nanosecond granularity
(s_time_gran == 1), and the inode atime/mtime setters store it verbatim
(only ctime is normalized, via inode_set_ctime_to_ts()). The
un-normalized value then corrupts on-disk metadata: ext4's
ext4_encode_extra_time() shifts tv_nsec left by EXT4_EPOCH_BITS, which
overflows the 32-bit extra field and clobbers the seconds-epoch bits, so
the stored seconds (and thus the year) are wrong on read-back. XFS with
bigtime mis-stores the timestamp for the same reason.
Validate the client-supplied atime/mtime in the proc handlers and return
NFS3ERR_INVAL before anything is changed. RFC 1813 lists NFS3ERR_INVAL
for SETATTR and describes it as the error for a value the server 'can
not store ... in its own representation'; the client maps it to EINVAL.
Checking in the proc handlers, rather than in nfsd_setattr(), keeps the
rejection in front of object creation. The create operations create the
object before nfsd_create_setattr() runs, so a late failure would leave
the new object behind and turn a non-idempotent request into a namespace
change that reports failure. The check is therefore done up front, for
the create operations before the object is created.
tv_nsec is a long, so the comparison casts it to unsigned long (the same
width) rather than to u32, matching timespec64_valid(). A u32 cast would
truncate on 64-bit; the unsigned long cast also rejects a value that
became negative when an out-of-range u32 wire nseconds was assigned to a
32-bit long.
Only client-supplied times are checked: SET_TO_SERVER_TIME requests
carry no client value. The sattrguard3 ctime is deliberately left alone:
an out-of-range guard simply never matches the object's ctime and yields
NFS3ERR_NOT_SYNC via the existing guardtime comparison, which is the
protocol-correct outcome rather than rejecting the request.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-89666 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-89666 的情报信息
请登录查看更多情报信息。
CVE-2026-89666 其他参考 (4)
同批安全公告 · Linux · 2026-09-11 · 共 431 条
| CVE-2026-89491 | OCFS2集群心跳锁持有期间睡眠漏洞 | |
| CVE-2026-89477 | Linux内核 SCTP 重配置空指针引用漏洞 | |
| CVE-2026-89478 | sctp：移除的传输中丢弃数据块 | |
| CVE-2026-89479 | 内核SCTP模块关联删除后仍处理报文 | |
| CVE-2026-89480 | NVMe-TCP 读取字节数异常拒绝漏洞 | |
| CVE-2026-89482 | NVMe-TCP 数据长度误判漏洞 | |
| CVE-2026-89481 | NVMe/TCP 主机内存泄露漏洞 | |
| CVE-2026-89483 | Linux内核 NVMe驱动 逻辑错误 | |
| CVE-2026-89484 | Linux内核lockd 空指针解引用漏洞 | |
| CVE-2026-89485 | Linux lockd 锁释放时文件指针固定漏洞 | |
| CVE-2026-89486 | IPMI 驱动 _ipmi_destroy_user 释放后使用漏洞 | |
| CVE-2026-89487 | Open vSwitch 数据包丢弃逻辑缺陷 | |
| CVE-2026-89488 | Open vSwitch CT limit 释放后使用漏洞 | |
| CVE-2026-89489 | OpenRISC 内核 or1k_atomic 任意内存访问漏洞 | |
| CVE-2026-89500 | ring-buffer 缓冲区读取页修复 | |
| CVE-2026-89497 | Orangefs 调试掩码解析空格处理缺陷 | |
| CVE-2026-89498 | Orangefs 双重释放漏洞 | |
| CVE-2026-89499 | ring-buffer 页面交换失败时停止远程读取 | |
| CVE-2026-89496 | ocfs2文件系统COW完成处理缺陷 | |
| CVE-2026-89501 | ring-buffer 子缓冲区调整时未持锁漏洞 |
显示前 20 条，共 431 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-89666
暂无评论