CVE-2026-92501— ext4文件系统 2.x 数据竞争漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
以下是该 Linux 内核漏洞描述的中文翻译： 在 Linux 内核中，以下漏洞已得到修复： ext4：在回退到缓冲写入之前，先排出正在进行的直接 I/O（DIO） 测试在 ext3（无 extent 的 inode）上开始间歇性失败。 该测试触发了“直接 I/O 的页缓存失效失败”警告，随后的 返回 。 如果在 中的 和 之间添加一个 50 毫秒的延迟，这个竞争条件就几乎总是可以复现。 背景与原因分析： 对于无 extent 的 inode，直接 I/O（DIO）写入空洞（hole）时无法使用“未写入”的 ext
可能的 ATT&CK 技术 1 AI
T1059 · Command and Scripting Interpreter影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 378f32bab3714f04c4e0c3aee4129f6703805550< fd7e0dab20837b9ea1eeef7c26f78ace8ac8258c |
affected |
378f32bab3714f04c4e0c3aee4129f6703805550< f0af3ae09fb72382da1a5371bf6761b0264668e4 |
affected | ||
378f32bab3714f04c4e0c3aee4129f6703805550< 7341e234927ff215f1d5d0bcfe04b74f53af378d |
affected | ||
378f32bab3714f04c4e0c3aee4129f6703805550< 74eee4ff9698a65b2e6e15dac0e50d6526ad5f20 |
affected | ||
378f32bab3714f04c4e0c3aee4129f6703805550< d47cdadd6e49023f7ee248048463807f1214f1ee |
affected | ||
378f32bab3714f04c4e0c3aee4129f6703805550< 4e4e3eec506247c8f8bd8aaa1eb25e67016681a5 |
affected | ||
378f32bab3714f04c4e0c3aee4129f6703805550< 9fd3ffc3c51c9deaba99bd7b338fff2d08f52416 |
affected | ||
378f32bab3714f04c4e0c3aee4129f6703805550< 15cdefd0c0522f9d5e12d947fa04f4c11649b699 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-92501 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
ext4: drain in-flight DIO before buffered write fallback
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
ext4: drain in-flight DIO before buffered write fallback
generic/746 started failing intermittently on ext3 (no-extent inodes).
The test triggers 'Page cache invalidation failure on direct I/O'
warnings and subsequent fsync returns -EIO. Adding a 50ms delay
between ext4_buffered_write_iter() and filemap_write_and_wait_range()
in ext4_dio_write_iter() makes the race almost always reproducible.
On no-extent inodes, DIO writes to holes cannot use unwritten extents,
so ext4_iomap_alloc() leaves m_flags=0 and ext4_map_blocks() returns 0.
The iomap layer then returns -ENOTBLK, causing fallback to buffered I/O.
The fallback path in ext4_dio_write_iter() calls
ext4_buffered_write_iter() which dirties pages, then does flush and
invalidate. However, there's an unprotected window between
ext4_buffered_write_iter() returning (with inode lock released) and
the subsequent flush+invalidate.
Concurrent async DIO completions from other threads can run
kiocb_invalidate_post_direct_write() during this window. If pages have
been re-dirtied, post-invalidation finds dirty pages and triggers the
warning, setting -EIO in the error sequence.
Consider a file with two 4k extents: [hole][written]. Thread A does
DIO to the written extent, while thread B does DIO spanning both:
kworker A (4k DIO, allocated block) kworker B (8k DIO, fallback)
----------------------------------- ----------------------------
inode_lock_shared() inode_lock_shared()
iomap_dio_rw(): iomap_dio_rw():
kiocb_invalidate_pages -> clean iomap_begin -> -ENOTBLK
submit_bio (async) dio->size = 0
inode_unlock_shared() inode_unlock_shared()
[bio pending in block layer] /* fallback: lock released */
ext4_buffered_write_iter()
inode_lock(exclusive)
generic_perform_write()
-> dirty pages [0, 8k]
inode_unlock(exclusive)
/* pages dirty, no lock */
[bio completes] filemap_write_and_wait_range()
iomap_dio_complete() -> flush dirty pages
kiocb_invalidate_post_direct_write() invalidate_mapping_pages()
invalidate_inode_pages2_range()
-> finds dirty page!
-> dio_warn_stale_pagecache()
-> errseq_set(-EIO)
This issue can be triggered through normal I/O paths, not just
intentionally overlapping DIO writes from userspace. For example,
generic/746 uses a loop device where multiple kworkers issue concurrent
I/O to the backing file. Additionally, when block_size < folio_size,
non-overlapping DIO writes that share a large folio can also trigger
the race.
Add inode_dio_wait() in ext4_buffered_write_iter() before
ext4_write_checks() to drain all in-flight DIO. This ensures that
all DIO clears existing pages before submitting IO (via
kiocb_invalidate_pages()), all BIO waits for all DIO to complete
(via inode_dio_wait()), and ext4_write_checks() observes the inode
size after all completed DIO so that ext4_block_zero_eof() does not
race with in-flight DIO, thus eliminating the race.
来源: 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-92501 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-92501 的情报信息
请登录查看更多情报信息。
CVE-2026-92501 补丁与修复 (8)
同批安全公告 · Linux · 2026-09-17 · 共 600 条
| CVE-2026-92489 | 9.8 CRITICAL | Linux内核 xfrm 双重释放漏洞 |
| CVE-2026-90235 | 9.8 CRITICAL | 内核sunrpc xprtsock并发读取修复 |
| CVE-2026-90173 | 9.8 CRITICAL | SMB SmbDirect 释放完成队列漏洞 |
| CVE-2026-90104 | 9.8 CRITICAL | NFSv4.1 解码前未清空调用列表 |
| CVE-2026-90151 | 9.8 CRITICAL | NFSv4客户端分配失败回调处理漏洞 |
| CVE-2026-90110 | 9.4 CRITICAL | inetpeer 随机化RB树节点比较 |
| CVE-2026-90230 | 9.1 CRITICAL | Linux内核Nvme-target堆越界读取漏洞 |
| CVE-2026-90414 | 9.1 CRITICAL | IB/isert拒绝声明超出实际接收数据的PDU |
| CVE-2026-90413 | 9.1 CRITICAL | IB/isert 登录PDU数据长度校验漏洞 |
| CVE-2026-90367 | 8.8 HIGH | Linux内核MT7996驱动死锁漏洞 |
| CVE-2026-90329 | 8.8 HIGH | Linux 内核 HID 驱动探测清理同步漏洞 |
| CVE-2026-93189 | 8.8 HIGH | Linux HID核心使用已释放内存漏洞 |
| CVE-2026-90240 | 8.8 HIGH | Linux内核 IOMMU 别名拆除时刷新缓存错误 |
| CVE-2026-90357 | 8.8 HIGH | mt76驱动MT7915无线局域网远程拒绝服务漏洞 |
| CVE-2026-90286 | 8.8 HIGH | AMDGPU GFX6 计算队列PFP使用漏洞 |
| CVE-2026-93042 | 8.8 HIGH | Linux内核dmaengine模块资源耗尽漏洞 |
| CVE-2026-90256 | 8.8 HIGH | Linux Bluetooth L2CAP 远程代码执行漏洞 |
| CVE-2026-90380 | 8.8 HIGH | MT76驱动 mt792x 使用释放后内存漏洞 |
| CVE-2026-90381 | 8.8 HIGH | Linux内核mt76驱动无线信道切换漏洞 |
| CVE-2026-90425 | 8.8 HIGH | Linux内核 5.x 内核漏洞 |
显示前 20 条，共 600 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-92501
暂无评论