CVE-2026-92500— ext4文件系统修复内联数据写入竞态条件
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已解决以下漏洞： ext4：使用 fsdata 跟踪内联数据写入状态并修复竞态条件 在 处理函数中，不再检查实时 inode 状态（即 和 ），而是通过地址空间操作的 参数，显式传递 阶段所准备的写入状态。 问题背景： 在 和 之间，并发线程（例如 ）可能会将内联数据转换为 extent。如果这种情况发生， 处理函数会错过内联数据写入路径，并落入基于 extent 的写入逻辑。然而，由于在 阶段从未分配块缓冲区（block buffers），这会导致 为 NULL，从而引发空指针解引用或数据
可能的 ATT&CK 技术 1 AI
T1015影响版本矩阵 8
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb< bd8d74bd46d09905164255b8635fa58b45f41068 |
affected |
3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb< 439aedfd7ae868d1d7b4930afe66091cb979cd5c |
affected | ||
3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb< 7edbb323bab2b2a609016014caafdb651c898249 |
affected | ||
3.8 |
affected | ||
< 3.8 |
unaffected | ||
6.18.52≤ 6.18.* |
unaffected | ||
7.2.6≤ 7.2.* |
unaffected | ||
7.3-rc1≤ * |
unaffected |
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-92500 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
ext4: use fsdata to track inline data write state and fix race
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
ext4: use fsdata to track inline data write state and fix race
Instead of checking the live inode state (ext4_has_inline_data(inode)
and ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA)) in the
write_end handlers, use the fsdata parameter of the address space
operations to explicitly pass down the state in which write_begin
prepared the write.
A concurrent thread (such as ext4_page_mkwrite()) can convert the
inline data to an extent between write_begin and write_end. If this
happens, the write_end handlers would previously miss the inline
write_end path and fall through to extent-based write_end logic.
However, since block buffers were never allocated in write_begin,
this resulted in NULL pointer dereferences or data loss because
folio_buffers(folio) was NULL.
Define EXT4_WRITE_DATA_INLINE (4) as a bit flag (Bit 2), treating
fsdata as bitwise flags rather than mutually exclusive enums to keep
states of the write path independent. Communicate this state via
fsdata:
1) ext4_write_begin() and ext4_da_write_begin() set the
EXT4_WRITE_DATA_INLINE bit in *fsdata via bitwise OR when an inline
write is successfully prepared.
2) On entry, ext4_write_begin() clears the EXT4_WRITE_DATA_INLINE bit
to safely handle VFS retries (where generic_perform_write() bypasses
the fsdata initialization on its retry jump).
3) The write_end handlers perform a bitwise AND to check if the
EXT4_WRITE_DATA_INLINE bit is set and invoke the inline write_end
helper accordingly.
Furthermore, during a buffered write, ext4_write_inline_data_end()
acquires the xattr lock after preparing the write. If a concurrent
page fault (ext4_page_mkwrite()) converts the inline data to an extent
after the write_end handlers check the state but before
ext4_write_inline_data_end() acquires the xattr write lock, the
subsequent check will trigger a kernel panic via
BUG_ON(!ext4_has_inline_data(inode)).
To keep git history working and bisectability clean, replace the
BUG_ON check in ext4_write_inline_data_end() with a graceful error-
handling retry path in this same commit. If the inline data is cleared
after locking the xattr, we safely release all resources (releasing
iloc.bh, unlocking/putting the folio, stopping the active journal
transaction handle) and return 0 (VFS retry) to let the generic write
path retry the operation safely.
来源: 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-92500 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-92500 的情报信息
请登录查看更多情报信息。
CVE-2026-92500 补丁与修复 (3)
同批安全公告 · 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-92500
暂无评论