CVE-2026-43118— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于日志重放时未正确更新i_size为0，可能导致零大小inode具有非零大小。
可能的 ATT&CK 技术 1 AI
T1070.003 · Clear Command History影响版本矩阵 8
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 12fcfd22fe5bf4fe74710232098bc101af497995< fddb157536e67a055597f00a8b4922d5f5ed0826 |
affected |
12fcfd22fe5bf4fe74710232098bc101af497995< 03e966b63df5b06790310c1faaf3e0cb43adea8b |
affected | ||
12fcfd22fe5bf4fe74710232098bc101af497995< 5254d4181add9dfaa5e3519edd71cc8f752b2f85 |
affected | ||
2.6.30 |
affected | ||
< 2.6.30 |
unaffected | ||
6.18.24≤ 6.18.* |
unaffected | ||
6.19.14≤ 6.19.* |
unaffected | ||
7.0≤ * |
unaffected |
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-43118 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
btrfs: fix zero size inode with non-zero size after log replay
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix zero size inode with non-zero size after log replay
When logging that an inode exists, as part of logging a new name or
logging new dir entries for a directory, we always set the generation of
the logged inode item to 0. This is to signal during log replay (in
overwrite_item()), that we should not set the i_size since we only logged
that an inode exists, so the i_size of the inode in the subvolume tree
must be preserved (as when we log new names or that an inode exists, we
don't log extents).
This works fine except when we have already logged an inode in full mode
or it's the first time we are logging an inode created in a past
transaction, that inode has a new i_size of 0 and then we log a new name
for the inode (due to a new hardlink or a rename), in which case we log
an i_size of 0 for the inode and a generation of 0, which causes the log
replay code to not update the inode's i_size to 0 (in overwrite_item()).
An example scenario:
mkdir /mnt/dir
xfs_io -f -c "pwrite 0 64K" /mnt/dir/foo
sync
xfs_io -c "truncate 0" -c "fsync" /mnt/dir/foo
ln /mnt/dir/foo /mnt/dir/bar
xfs_io -c "fsync" /mnt/dir
<power fail>
After log replay the file remains with a size of 64K. This is because when
we first log the inode, when we fsync file foo, we log its current i_size
of 0, and then when we create a hard link we log again the inode in exists
mode (LOG_INODE_EXISTS) but we set a generation of 0 for the inode item we
add to the log tree, so during log replay overwrite_item() sees that the
generation is 0 and i_size is 0 so we skip updating the inode's i_size
from 64K to 0.
Fix this by making sure at fill_inode_item() we always log the real
generation of the inode if it was logged in the current transaction with
the i_size we logged before. Also if an inode created in a previous
transaction is logged in exists mode only, make sure we log the i_size
stored in the inode item located from the commit root, so that if we log
multiple times that the inode exists we get the correct i_size.
A test case for fstests will follow soon.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于日志重放时未正确更新i_size为0，可能导致零大小inode具有非零大小。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-43118 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-43118 的情报信息
请登录查看更多情报信息。
CVE-2026-43118 补丁与修复 (3)
同批安全公告 · Linux · 2026-05-06 · 共 224 条
| CVE-2026-43208 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43125 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43198 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43186 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43185 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43114 | 9.4 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43117 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43197 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43083 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43158 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43112 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43113 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43110 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43249 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43239 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43232 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43283 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43172 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43176 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43215 | 8.8 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 224 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-43118
暂无评论