CVE-2024-45003— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于处理inode回收时，文件系统可能发生死锁。
可能的 ATT&CK 技术 1 AI
T1499 · Endpoint Denial of Service影响版本矩阵 16
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | e50e5129f384ae282adebfb561189cdb19b81cee< 3525ad25240dfdd8c78f3470911ed10aa727aa72 |
affected |
e50e5129f384ae282adebfb561189cdb19b81cee< 03880af02a78bc9a98b5a581f529cf709c88a9b8 |
affected | ||
e50e5129f384ae282adebfb561189cdb19b81cee< cda54ec82c0f9d05393242b20b13f69b083f7e88 |
affected | ||
e50e5129f384ae282adebfb561189cdb19b81cee< 437741eba63bf4e437e2beb5583f8633556a2b98 |
affected | ||
e50e5129f384ae282adebfb561189cdb19b81cee< b9bda5f6012dd00372f3a06a82ed8971a4c57c32 |
affected | ||
e50e5129f384ae282adebfb561189cdb19b81cee< 9063ab49c11e9518a3f2352434bb276cc8134c5f |
affected | ||
e50e5129f384ae282adebfb561189cdb19b81cee< 2a0629834cd82f05d424bbc193374f9a43d1f87d |
affected | ||
4.13 |
affected | ||
| … +8 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2024-45003 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
vfs: Don't evict inode under the inode lru traversing context
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
vfs: Don't evict inode under the inode lru traversing context
The inode reclaiming process(See function prune_icache_sb) collects all
reclaimable inodes and mark them with I_FREEING flag at first, at that
time, other processes will be stuck if they try getting these inodes
(See function find_inode_fast), then the reclaiming process destroy the
inodes by function dispose_list(). Some filesystems(eg. ext4 with
ea_inode feature, ubifs with xattr) may do inode lookup in the inode
evicting callback function, if the inode lookup is operated under the
inode lru traversing context, deadlock problems may happen.
Case 1: In function ext4_evict_inode(), the ea inode lookup could happen
if ea_inode feature is enabled, the lookup process will be stuck
under the evicting context like this:
1. File A has inode i_reg and an ea inode i_ea
2. getfattr(A, xattr_buf) // i_ea is added into lru // lru->i_ea
3. Then, following three processes running like this:
PA PB
echo 2 > /proc/sys/vm/drop_caches
shrink_slab
prune_dcache_sb
// i_reg is added into lru, lru->i_ea->i_reg
prune_icache_sb
list_lru_walk_one
inode_lru_isolate
i_ea->i_state |= I_FREEING // set inode state
inode_lru_isolate
__iget(i_reg)
spin_unlock(&i_reg->i_lock)
spin_unlock(lru_lock)
rm file A
i_reg->nlink = 0
iput(i_reg) // i_reg->nlink is 0, do evict
ext4_evict_inode
ext4_xattr_delete_inode
ext4_xattr_inode_dec_ref_all
ext4_xattr_inode_iget
ext4_iget(i_ea->i_ino)
iget_locked
find_inode_fast
__wait_on_freeing_inode(i_ea) ----→ AA deadlock
dispose_list // cannot be executed by prune_icache_sb
wake_up_bit(&i_ea->i_state)
Case 2: In deleted inode writing function ubifs_jnl_write_inode(), file
deleting process holds BASEHD's wbuf->io_mutex while getting the
xattr inode, which could race with inode reclaiming process(The
reclaiming process could try locking BASEHD's wbuf->io_mutex in
inode evicting function), then an ABBA deadlock problem would
happen as following:
1. File A has inode ia and a xattr(with inode ixa), regular file B has
inode ib and a xattr.
2. getfattr(A, xattr_buf) // ixa is added into lru // lru->ixa
3. Then, following three processes running like this:
PA PB PC
echo 2 > /proc/sys/vm/drop_caches
shrink_slab
prune_dcache_sb
// ib and ia are added into lru, lru->ixa->ib->ia
prune_icache_sb
list_lru_walk_one
inode_lru_isolate
ixa->i_state |= I_FREEING // set inode state
inode_lru_isolate
__iget(ib)
spin_unlock(&ib->i_lock)
spin_unlock(lru_lock)
rm file B
ib->nlink = 0
rm file A
iput(ia)
ubifs_evict_inode(ia)
ubifs_jnl_delete_inode(ia)
ubifs_jnl_write_inode(ia)
make_reservation(BASEHD) // Lock wbuf->io_mutex
ubifs_iget(ixa->i_ino)
iget_locked
find_inode_fast
__wait_on_freeing_inode(ixa)
| iput(ib) // ib->nlink is 0, do evict
| ubifs_evict_inode
| ubifs_jnl_delete_inode(ib)
↓ ubifs_jnl_write_inode
ABBA deadlock ←-----make_reservation(BASEHD)
dispose_list // cannot be executed by prune_icache_sb
wake_up_bit(&ixa->i_state)
Fix the possible deadlock by using new inode state flag I_LRU_ISOLATING
to pin the inode in memory while inode_lru_isolate(
---truncated---
来源: 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存在安全漏洞，该漏洞源于处理inode回收时，文件系统可能发生死锁。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2024-45003 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2024-45003 的情报信息
请登录查看更多情报信息。
CVE-2024-45003 补丁与修复 (5)
同批安全公告 · Linux · 2024-09-04 · 共 58 条
| CVE-2024-44984 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-44998 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-44985 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-44970 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-44994 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44988 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44986 | 8.1 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44973 | 8.1 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44966 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44949 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44959 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44951 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44954 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44967 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44974 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44978 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44987 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44995 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-44997 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-45000 | 7.8 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 58 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2024-45003
暂无评论