CVE-2024-42148— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞，该漏洞源于bnx2x模块中在使用具有32个以上物理CPU核心的系统或定义的以太网队列数量大于或等于FP_SB_MAX_E1x时，发生UBSAN数组索引越界。
可能的 ATT&CK 技术 1 AI
T1498 · Network Denial of Service影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 50f0a562f8cc9ed9d9f7f7380434c3c8646172d5< cfb04472ce33bee2579caf4dc9f4242522f6e26e |
affected |
50f0a562f8cc9ed9d9f7f7380434c3c8646172d5< cbe53087026ad929cd3950508397e8892a6a2a0f |
affected | ||
50f0a562f8cc9ed9d9f7f7380434c3c8646172d5< 8b17cec33892a66bbd71f8d9a70a45e2072ae84f |
affected | ||
50f0a562f8cc9ed9d9f7f7380434c3c8646172d5< 0edae06b4c227bcfaf3ce21208d49191e1009d3b |
affected | ||
50f0a562f8cc9ed9d9f7f7380434c3c8646172d5< 9504a1550686f53b0bab4cab31d435383b1ee2ce |
affected | ||
50f0a562f8cc9ed9d9f7f7380434c3c8646172d5< f1313ea92f82451923e28ab45a4aaa0e70e80b98 |
affected | ||
50f0a562f8cc9ed9d9f7f7380434c3c8646172d5< b9ea38e767459111a511ed4fb74abc37db95a59d |
affected | ||
50f0a562f8cc9ed9d9f7f7380434c3c8646172d5< 134061163ee5ca4759de5c24ca3bd71608891ba7 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2024-42148 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
bnx2x: Fix multiple UBSAN array-index-out-of-bounds
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
bnx2x: Fix multiple UBSAN array-index-out-of-bounds
Fix UBSAN warnings that occur when using a system with 32 physical
cpu cores or more, or when the user defines a number of Ethernet
queues greater than or equal to FP_SB_MAX_E1x using the num_queues
module parameter.
Currently there is a read/write out of bounds that occurs on the array
"struct stats_query_entry query" present inside the "bnx2x_fw_stats_req"
struct in "drivers/net/ethernet/broadcom/bnx2x/bnx2x.h".
Looking at the definition of the "struct stats_query_entry query" array:
struct stats_query_entry query[FP_SB_MAX_E1x+
BNX2X_FIRST_QUEUE_QUERY_IDX];
FP_SB_MAX_E1x is defined as the maximum number of fast path interrupts and
has a value of 16, while BNX2X_FIRST_QUEUE_QUERY_IDX has a value of 3
meaning the array has a total size of 19.
Since accesses to "struct stats_query_entry query" are offset-ted by
BNX2X_FIRST_QUEUE_QUERY_IDX, that means that the total number of Ethernet
queues should not exceed FP_SB_MAX_E1x (16). However one of these queues
is reserved for FCOE and thus the number of Ethernet queues should be set
to [FP_SB_MAX_E1x -1] (15) if FCOE is enabled or [FP_SB_MAX_E1x] (16) if
it is not.
This is also described in a comment in the source code in
drivers/net/ethernet/broadcom/bnx2x/bnx2x.h just above the Macro definition
of FP_SB_MAX_E1x. Below is the part of this explanation that it important
for this patch
/*
* The total number of L2 queues, MSIX vectors and HW contexts (CIDs) is
* control by the number of fast-path status blocks supported by the
* device (HW/FW). Each fast-path status block (FP-SB) aka non-default
* status block represents an independent interrupts context that can
* serve a regular L2 networking queue. However special L2 queues such
* as the FCoE queue do not require a FP-SB and other components like
* the CNIC may consume FP-SB reducing the number of possible L2 queues
*
* If the maximum number of FP-SB available is X then:
* a. If CNIC is supported it consumes 1 FP-SB thus the max number of
* regular L2 queues is Y=X-1
* b. In MF mode the actual number of L2 queues is Y= (X-1/MF_factor)
* c. If the FCoE L2 queue is supported the actual number of L2 queues
* is Y+1
* d. The number of irqs (MSIX vectors) is either Y+1 (one extra for
* slow-path interrupts) or Y+2 if CNIC is supported (one additional
* FP interrupt context for the CNIC).
* e. The number of HW context (CID count) is always X or X+1 if FCoE
* L2 queue is supported. The cid for the FCoE L2 queue is always X.
*/
However this driver also supports NICs that use the E2 controller which can
handle more queues due to having more FP-SB represented by FP_SB_MAX_E2.
Looking at the commits when the E2 support was added, it was originally
using the E1x parameters: commit f2e0899f0f27 ("bnx2x: Add 57712 support").
Back then FP_SB_MAX_E2 was set to 16 the same as E1x. However the driver
was later updated to take full advantage of the E2 instead of having it be
limited to the capabilities of the E1x. But as far as we can tell, the
array "stats_query_entry query" was still limited to using the FP-SB
available to the E1x cards as part of an oversignt when the driver was
updated to take full advantage of the E2, and now with the driver being
aware of the greater queue size supported by E2 NICs, it causes the UBSAN
warnings seen in the stack traces below.
This patch increases the size of the "stats_query_entry query" array by
replacing FP_SB_MAX_E1x with FP_SB_MAX_E2 to be large enough to handle
both types of NICs.
Stack traces:
UBSAN: array-index-out-of-bounds in
drivers/net/ethernet/broadcom/bnx2x/bnx2x_stats.c:1529:11
index 20 is out of range for type 'stats_query_entry [19]'
CPU: 12 PID: 858 Comm: systemd-network Not tainted 6.9.0-060900rc7-generic
#202405052133
Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360
---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 存在安全漏洞，该漏洞源于bnx2x模块中在使用具有32个以上物理CPU核心的系统或定义的以太网队列数量大于或等于FP_SB_MAX_E1x时，发生UBSAN数组索引越界。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2024-42148 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2024-42148 的情报信息
请登录查看更多情报信息。
CVE-2024-42148 其他参考 (8)
同批安全公告 · Linux · 2024-07-30 · 共 70 条
| CVE-2024-42108 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-42225 | 8.3 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42120 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42115 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42112 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42111 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42109 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42105 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42104 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42103 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42117 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42162 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42099 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42132 | 7.6 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42133 | 7.6 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42152 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42110 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42145 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42123 | 7.0 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-42224 | 7.0 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 70 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2024-42148
暂无评论