CVE-2026-74384— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会开源的一个操作系统内核。 Linux kernel存在安全漏洞，该漏洞源于对结构体nvme_ns_head中灵活数组成员current_path[]的分配大小计算错误，在NUMA节点ID稀疏的系统上可能导致数组越界访问，从而引发系统崩溃或内存破坏。
影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | f333444708f82c4a4d3ccac004da0bfd9cfdfa42< 7e7b167e65610dfa7564d449474f4b477f9d4c1c |
affected |
f333444708f82c4a4d3ccac004da0bfd9cfdfa42< 316b5f1168264844aa125959de1d6da2b1905795 |
affected | ||
f333444708f82c4a4d3ccac004da0bfd9cfdfa42< 1d4131b5c9823c7d2c86389898ad1b466af7df5e |
affected | ||
f333444708f82c4a4d3ccac004da0bfd9cfdfa42< 9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5 |
affected | ||
f333444708f82c4a4d3ccac004da0bfd9cfdfa42< bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6 |
affected | ||
f333444708f82c4a4d3ccac004da0bfd9cfdfa42< 140d6fff4ed266592492a23444043842b4af7a62 |
affected | ||
f333444708f82c4a4d3ccac004da0bfd9cfdfa42< 7173a741fed73de6247384056fe92e582ba12507 |
affected | ||
f333444708f82c4a4d3ccac004da0bfd9cfdfa42< 001e57554de81aa79c25c18fd53911d8a415c304 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-74384 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
nvme-multipath: fix flex array size in struct nvme_ns_head
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
nvme-multipath: fix flex array size in struct nvme_ns_head
struct nvme_ns_head contains a flexible array member, current_path[],
which is indexed using the NUMA node ID:
head->current_path[numa_node_id()]
The structure is currently allocated as:
size = sizeof(struct nvme_ns_head) +
(num_possible_nodes() * sizeof(struct nvme_ns *));
head = kzalloc(size, GFP_KERNEL);
This allocation assumes that NUMA node IDs are sequential and densely
packed from 0 .. num_possible_nodes() - 1. While this assumption holds
on many systems, it is not always true on some architectures such as
powerpc.
On some powerpc systems, NUMA node IDs can be sparse. For example:
NUMA:
NUMA node(s): 6
NUMA node0 CPU(s): 80-159
NUMA node8 CPU(s): 0-79
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):
That is, the possible/online NUMA node IDs are: 0, 8, 252, 253, 254, 255
In this case: num_possible_nodes() = 6
So memory is allocated for only 6 entries in current_path[]. However,
the array is later indexed using the actual NUMA node ID. As a result,
accesses such as:
head->current_path[8] or
head->current_path[252]
goes out of bounds, leading to the following KASAN splat:
==================================================================
BUG: KASAN: slab-out-of-bounds in nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]
Write of size 8 at addr c00020003bda35b8 by task kworker/u641:2/1997
CPU: 1 UID: 0 PID: 1997 Comm: kworker/u641:2 Not tainted 7.1.0-rc5-dirty #14 PREEMPT(lazy)
Hardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV
Workqueue: async async_run_entry_fn
Call Trace:
[c000200037fa7510] [c0000000021c23d4] dump_stack_lvl+0x88/0xdc (unreliable)
[c000200037fa7540] [c0000000009fda90] print_report+0x22c/0x67c
[c000200037fa7630] [c0000000009fd508] kasan_report+0x108/0x220
[c000200037fa7740] [c0000000009fff48] __asan_store8+0xe8/0x120
[c000200037fa7760] [c008000018e76474] nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]
[c000200037fa7800] [c008000018e6556c] nvme_update_ns_info+0x4a4/0x5e0 [nvme_core]
[c000200037fa7a50] [c008000018e66270] nvme_alloc_ns+0x6d8/0x1a70 [nvme_core]
[c000200037fa7c20] [c008000018e679fc] nvme_scan_ns+0x3f4/0x630 [nvme_core]
[c000200037fa7d10] [c00000000031f22c] async_run_entry_fn+0x9c/0x3a0
[c000200037fa7db0] [c0000000002fa544] process_one_work+0x414/0xa10
[c000200037fa7ec0] [c0000000002fbf00] worker_thread+0x320/0x640
[c000200037fa7f80] [c00000000030d0f8] kthread+0x278/0x290
[c000200037fa7fe0] [c00000000000ded8] start_kernel_thread+0x14/0x18
Allocated by task 1997 on cpu 1 at 35.928317s:
The buggy address belongs to the object at c00020003bda3000
which belongs to the cache kmalloc-rnd-15-2k of size 2048
The buggy address is located 16 bytes to the right of
allocated 1448-byte region [c00020003bda3000, c00020003bda35a8)
The buggy address belongs to the physical page:
Memory state around the buggy address:
c00020003bda3480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c00020003bda3500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>c00020003bda3580: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc
^
c00020003bda3600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
c00020003bda3680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
Fix this by allocating the flexible array using nr_node_ids instead
of num_possible_nodes(). Since nr_node_ids represents the maximum
possible NUMA node IDs, indexing current_path[] using numa_node_id()
becomes safe even on systems with sparse node IDs.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/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 kernel存在安全漏洞，该漏洞源于对结构体nvme_ns_head中灵活数组成员current_path[]的分配大小计算错误，在NUMA节点ID稀疏的系统上可能导致数组越界访问，从而引发系统崩溃或内存破坏。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-74384 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-74384 的情报信息
请登录查看更多情报信息。
CVE-2026-74384 补丁与修复 (7)
CVE-2026-74384 其他参考 (1)
同批安全公告 · Linux · 2026-08-15 · 共 845 条
| CVE-2026-72421 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72408 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-74309 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72407 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-74279 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-74475 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-74280 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72493 | 9.9 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-74361 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-74268 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72064 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72065 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72069 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72185 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72249 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72494 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72248 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72491 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-72251 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-74480 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
显示前 20 条，共 845 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-74384
暂无评论