CVE-2024-53171— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于ubifs:authentication模块中ubifs_tnc_end_commit函数中未正确更新cparent指针，可能导致释放后重用。
可能的 ATT&CK 技术 1 AI
T1499 · Endpoint Denial of Service影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 16a26b20d2afd0cf063816725b45b12e78d5bb31< daac4aa1825de0dbc1a6eede2fa7f9fc53f14223 |
affected |
16a26b20d2afd0cf063816725b45b12e78d5bb31< 8d8b3f5f4cbfbf6cb0ea4a4d5dc296872b4151eb |
affected | ||
16a26b20d2afd0cf063816725b45b12e78d5bb31< 4d9807048b851d7a58d5bd089c16254af896e4df |
affected | ||
16a26b20d2afd0cf063816725b45b12e78d5bb31< 74981f7577d183acad1cd58f74c10d263711a215 |
affected | ||
16a26b20d2afd0cf063816725b45b12e78d5bb31< 01d3a2293d7e4edfff96618c15727db7e51f11b6 |
affected | ||
16a26b20d2afd0cf063816725b45b12e78d5bb31< 398a91599d263e41c5f95a2fd4ebdb6280b5c6c3 |
affected | ||
16a26b20d2afd0cf063816725b45b12e78d5bb31< 2497479aecebe869d23a0064e0fd1a03e34f0e2a |
affected | ||
16a26b20d2afd0cf063816725b45b12e78d5bb31< 4617fb8fc15effe8eda4dd898d4e33eb537a7140 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2024-53171 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit
After an insertion in TNC, the tree might split and cause a node to
change its `znode->parent`. A further deletion of other nodes in the
tree (which also could free the nodes), the aforementioned node's
`znode->cparent` could still point to a freed node. This
`znode->cparent` may not be updated when getting nodes to commit in
`ubifs_tnc_start_commit()`. This could then trigger a use-after-free
when accessing the `znode->cparent` in `write_index()` in
`ubifs_tnc_end_commit()`.
This can be triggered by running
rm -f /etc/test-file.bin
dd if=/dev/urandom of=/etc/test-file.bin bs=1M count=60 conv=fsync
in a loop, and with `CONFIG_UBIFS_FS_AUTHENTICATION`. KASAN then
reports:
BUG: KASAN: use-after-free in ubifs_tnc_end_commit+0xa5c/0x1950
Write of size 32 at addr ffffff800a3af86c by task ubifs_bgt0_20/153
Call trace:
dump_backtrace+0x0/0x340
show_stack+0x18/0x24
dump_stack_lvl+0x9c/0xbc
print_address_description.constprop.0+0x74/0x2b0
kasan_report+0x1d8/0x1f0
kasan_check_range+0xf8/0x1a0
memcpy+0x84/0xf4
ubifs_tnc_end_commit+0xa5c/0x1950
do_commit+0x4e0/0x1340
ubifs_bg_thread+0x234/0x2e0
kthread+0x36c/0x410
ret_from_fork+0x10/0x20
Allocated by task 401:
kasan_save_stack+0x38/0x70
__kasan_kmalloc+0x8c/0xd0
__kmalloc+0x34c/0x5bc
tnc_insert+0x140/0x16a4
ubifs_tnc_add+0x370/0x52c
ubifs_jnl_write_data+0x5d8/0x870
do_writepage+0x36c/0x510
ubifs_writepage+0x190/0x4dc
__writepage+0x58/0x154
write_cache_pages+0x394/0x830
do_writepages+0x1f0/0x5b0
filemap_fdatawrite_wbc+0x170/0x25c
file_write_and_wait_range+0x140/0x190
ubifs_fsync+0xe8/0x290
vfs_fsync_range+0xc0/0x1e4
do_fsync+0x40/0x90
__arm64_sys_fsync+0x34/0x50
invoke_syscall.constprop.0+0xa8/0x260
do_el0_svc+0xc8/0x1f0
el0_svc+0x34/0x70
el0t_64_sync_handler+0x108/0x114
el0t_64_sync+0x1a4/0x1a8
Freed by task 403:
kasan_save_stack+0x38/0x70
kasan_set_track+0x28/0x40
kasan_set_free_info+0x28/0x4c
__kasan_slab_free+0xd4/0x13c
kfree+0xc4/0x3a0
tnc_delete+0x3f4/0xe40
ubifs_tnc_remove_range+0x368/0x73c
ubifs_tnc_remove_ino+0x29c/0x2e0
ubifs_jnl_delete_inode+0x150/0x260
ubifs_evict_inode+0x1d4/0x2e4
evict+0x1c8/0x450
iput+0x2a0/0x3c4
do_unlinkat+0x2cc/0x490
__arm64_sys_unlinkat+0x90/0x100
invoke_syscall.constprop.0+0xa8/0x260
do_el0_svc+0xc8/0x1f0
el0_svc+0x34/0x70
el0t_64_sync_handler+0x108/0x114
el0t_64_sync+0x1a4/0x1a8
The offending `memcpy()` in `ubifs_copy_hash()` has a use-after-free
when a node becomes root in TNC but still has a `cparent` to an already
freed node. More specifically, consider the following TNC:
zroot
/
/
zp1
/
/
zn
Inserting a new node `zn_new` with a key smaller then `zn` will trigger
a split in `tnc_insert()` if `zp1` is full:
zroot
/ \
/ \
zp1 zp2
/ \
/ \
zn_new zn
`zn->parent` has now been moved to `zp2`, *but* `zn->cparent` still
points to `zp1`.
Now, consider a removal of all the nodes _except_ `zn`. Just when
`tnc_delete()` is about to delete `zroot` and `zp2`:
zroot
\
\
zp2
\
\
zn
`zroot` and `zp2` get freed and the tree collapses:
zn
`zn` now becomes the new `zroot`.
`get_znodes_to_commit()` will now only find `zn`, the new `zroot`, and
`write_index()` will check its `znode->cparent` that wrongly points to
the already freed `zp1`. `ubifs_copy_hash()` thus gets wrongly called
with `znode->cparent->zbranch[znode->iip].hash` that triggers the
use-after-free!
Fix this by explicitly setting `znode->cparent` to `NULL` in
`get_znodes_to_commit()` for the root node. The search for the dirty
nodes
---truncated---
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
来源: 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存在安全漏洞，该漏洞源于ubifs:authentication模块中ubifs_tnc_end_commit函数中未正确更新cparent指针，可能导致释放后重用。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2024-53171 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2024-53171 的情报信息
请登录查看更多情报信息。
CVE-2024-53171 补丁与修复 (8)
同批安全公告 · Linux · 2024-12-27 · 共 221 条
| CVE-2024-53186 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-56645 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-53169 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-56656 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-53179 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-53209 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-53206 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-56640 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-53176 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-53177 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-56591 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56626 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56669 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-53237 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-53224 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56651 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56653 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56627 | 8.1 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56538 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56624 | 7.8 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 221 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2024-53171
暂无评论