{"id":7336,"date":"2026-09-04T18:49:30","date_gmt":"2026-09-04T10:49:30","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-74384"},"modified":"2026-09-04T18:49:30","modified_gmt":"2026-09-04T10:49:30","slug":"cve-2026-74384","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-74384","title":{"rendered":"CVE-2026-74384 [CRITICAL] &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix f"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>nvme-multipath: fix flex array size in struct nvme_ns_head<\/p>\n<p>struct nvme_ns_head contains a flexible array member, current_path[],<br \/>\nwhich is indexed using the NUMA node ID:<br \/>\nhead-&gt;current_path[numa_node_id()]<\/p>\n<p>The structure is currently allocated as:<br \/>\nsize = sizeof(struct nvme_ns_head) +<br \/>\n       (num_possible_nodes() * sizeof(struct nvme_ns *));<br \/>\nhead = kzalloc(size, GFP_KERNEL);<\/p>\n<p>This allocation assumes that NUMA node IDs are sequential and densely<br \/>\npacked from 0 .. num_possible_nodes() &#8211; 1. While this assumption holds<br \/>\non many systems, it is not always true on some architectures such as<br \/>\npowerpc.<\/p>\n<p>On some powerpc systems, NUMA node IDs can be sparse. For example:<br \/>\nNUMA:<br \/>\n  NUMA node(s):              6<br \/>\n  NUMA node0 CPU(s):         80-159<br \/>\n  NUMA node8 CPU(s):         0-79<br \/>\n  NUMA node252 CPU(s):<br \/>\n  NUMA node253 CPU(s):<br \/>\n  NUMA node254 CPU(s):<br \/>\n  NUMA node255 CPU(s):<\/p>\n<p>That is, the possible\/online NUMA node IDs are: 0, 8, 252, 253, 254, 255<br \/>\nIn this case: num_possible_nodes() = 6<\/p>\n<p>So memory is allocated for only 6 entries in current_path[]. However,<br \/>\nthe array is later indexed using the actual NUMA node ID. As a result,<br \/>\naccesses such as:<br \/>\nhead-&gt;current_path[8] or<br \/>\nhead-&gt;current_path[252]<br \/>\ngoes out of bounds, leading to the following KASAN splat:<\/p>\n<p>==================================================================<br \/>\nBUG: KASAN: slab-out-of-bounds in nvme_mpath_revalidate_paths+0x22c\/0x290 [nvme_core]<br \/>\nWrite of size 8 at addr c00020003bda35b8 by task kworker\/u641:2\/1997<\/p>\n<p>CPU: 1 UID: 0 PID: 1997 Comm: kworker\/u641:2 Not tainted 7.1.0-rc5-dirty #14 PREEMPT(lazy)<br \/>\nHardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV<br \/>\nWorkqueue: async async_run_entry_fn<br \/>\nCall Trace:<br \/>\n[c000200037fa7510] [c0000000021c23d4] dump_stack_lvl+0x88\/0xdc (unreliable)<br \/>\n[c000200037fa7540] [c0000000009fda90] print_report+0x22c\/0x67c<br \/>\n[c000200037fa7630] [c0000000009fd508] kasan_report+0x108\/0x220<br \/>\n[c000200037fa7740] [c0000000009fff48] __asan_store8+0xe8\/0x120<br \/>\n[c000200037fa7760] [c008000018e76474] nvme_mpath_revalidate_paths+0x22c\/0x290 [nvme_core]<br \/>\n[c000200037fa7800] [c008000018e6556c] nvme_update_ns_info+0x4a4\/0x5e0 [nvme_core]<br \/>\n[c000200037fa7a50] [c008000018e66270] nvme_alloc_ns+0x6d8\/0x1a70 [nvme_core]<br \/>\n[c000200037fa7c20] [c008000018e679fc] nvme_scan_ns+0x3f4\/0x630 [nvme_core]<br \/>\n[c000200037fa7d10] [c00000000031f22c] async_run_entry_fn+0x9c\/0x3a0<br \/>\n[c000200037fa7db0] [c0000000002fa544] process_one_work+0x414\/0xa10<br \/>\n[c000200037fa7ec0] [c0000000002fbf00] worker_thread+0x320\/0x640<br \/>\n[c000200037fa7f80] [c00000000030d0f8] kthread+0x278\/0x290<br \/>\n[c000200037fa7fe0] [c00000000000ded8] start_kernel_thread+0x14\/0x18<\/p>\n<p>Allocated by task 1997 on cpu 1 at 35.928317s:<\/p>\n<p>The buggy address belongs to the object at c00020003bda3000<br \/>\n which belongs to the cache kmalloc-rnd-15-2k of size 2048<br \/>\nThe buggy address is located 16 bytes to the right of<br \/>\n allocated 1448-byte region [c00020003bda3000, c00020003bda35a8)<\/p>\n<p>The buggy address belongs to the physical page:<\/p>\n<p>Memory state around the buggy address:<br \/>\n c00020003bda3480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br \/>\n c00020003bda3500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00<br \/>\n&gt;c00020003bda3580: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc<br \/>\n                                        ^<br \/>\n c00020003bda3600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc<br \/>\n c00020003bda3680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc<br \/>\n==================================================================<\/p>\n<p>Fix this by allocating the flexible array using nr_node_ids instead<br \/>\nof num_possible_nodes(). Since nr_node_ids represents the maximum<br \/>\npossible NUMA node IDs, indexing current_path[] using numa_node_id()<br \/>\nbecomes safe even on systems with sparse node IDs.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>nvme-multipath: fix flex array size in struct nvme_ns_head<\/p>\n<p>struct nvme_ns_head contains a flexible array member, current_path[],<br \/>\nw<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-7336","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/7336","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7336"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7336"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7336"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}