CVE-2024-53680— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于ip_vs_protocol_init函数中未初始化的栈缓冲区，可能导致未定义行为（UB）。
影响版本矩阵 16
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 31d1ddc1ce8e8d3f101a679243abb42a313ee88a |
affected |
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 0b2cbed82b7c6504a8a0fbd181f92dd56b432c12 |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< d6e1776f51c95827142f1d7064118e255e2deec1 |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 664d0feab92495b6a27edc3d1119e232c0fe8b2b |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 124834133b32f9386bb2d8581d9ab92f65e951e4 |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 48130002e64fd191b7d18efeb4d253fcc23e4688 |
affected | ||
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2< 146b6f1112eb30a19776d6c323c994e9d67790db |
affected | ||
2.6.12 |
affected | ||
| … +8 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2024-53680 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init()
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init()
Under certain kernel configurations when building with Clang/LLVM, the
compiler does not generate a return or jump as the terminator
instruction for ip_vs_protocol_init(), triggering the following objtool
warning during build time:
vmlinux.o: warning: objtool: ip_vs_protocol_init() falls through to next function __initstub__kmod_ip_vs_rr__935_123_ip_vs_rr_init6()
At runtime, this either causes an oops when trying to load the ipvs
module or a boot-time panic if ipvs is built-in. This same issue has
been reported by the Intel kernel test robot previously.
Digging deeper into both LLVM and the kernel code reveals this to be a
undefined behavior problem. ip_vs_protocol_init() uses a on-stack buffer
of 64 chars to store the registered protocol names and leaves it
uninitialized after definition. The function calls strnlen() when
concatenating protocol names into the buffer. With CONFIG_FORTIFY_SOURCE
strnlen() performs an extra step to check whether the last byte of the
input char buffer is a null character (commit 3009f891bb9f ("fortify:
Allow strlen() and strnlen() to pass compile-time known lengths")).
This, together with possibly other configurations, cause the following
IR to be generated:
define hidden i32 @ip_vs_protocol_init() local_unnamed_addr #5 section ".init.text" align 16 !kcfi_type !29 {
%1 = alloca [64 x i8], align 16
...
14: ; preds = %11
%15 = getelementptr inbounds i8, ptr %1, i64 63
%16 = load i8, ptr %15, align 1
%17 = tail call i1 @llvm.is.constant.i8(i8 %16)
%18 = icmp eq i8 %16, 0
%19 = select i1 %17, i1 %18, i1 false
br i1 %19, label %20, label %23
20: ; preds = %14
%21 = call i64 @strlen(ptr noundef nonnull dereferenceable(1) %1) #23
...
23: ; preds = %14, %11, %20
%24 = call i64 @strnlen(ptr noundef nonnull dereferenceable(1) %1, i64 noundef 64) #24
...
}
The above code calculates the address of the last char in the buffer
(value %15) and then loads from it (value %16). Because the buffer is
never initialized, the LLVM GVN pass marks value %16 as undefined:
%13 = getelementptr inbounds i8, ptr %1, i64 63
br i1 undef, label %14, label %17
This gives later passes (SCCP, in particular) more DCE opportunities by
propagating the undef value further, and eventually removes everything
after the load on the uninitialized stack location:
define hidden i32 @ip_vs_protocol_init() local_unnamed_addr #0 section ".init.text" align 16 !kcfi_type !11 {
%1 = alloca [64 x i8], align 16
...
12: ; preds = %11
%13 = getelementptr inbounds i8, ptr %1, i64 63
unreachable
}
In this way, the generated native code will just fall through to the
next function, as LLVM does not generate any code for the unreachable IR
instruction and leaves the function without a terminator.
Zero the on-stack buffer to avoid this possible UB.
来源: 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存在安全漏洞，该漏洞源于ip_vs_protocol_init函数中未初始化的栈缓冲区，可能导致未定义行为（UB）。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2024-53680 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2024-53680 的情报信息
请登录查看更多情报信息。
CVE-2024-53680 补丁与修复 (7)
同批安全公告 · Linux · 2025-01-11 · 共 67 条
| CVE-2024-47408 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-49568 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-57843 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-57793 | 9.3 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-49571 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-55639 | 8.4 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-41149 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-57849 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-57850 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-52319 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-51729 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-57875 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-47794 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-49569 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56788 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-57791 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-57804 | 7.3 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-57792 | 7.3 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-56368 | 7.1 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-49573 | 7.0 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 67 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2024-53680
暂无评论