CVE-2026-74384

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-74384", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-08-15T05:44:03.890Z", "datePublished": "2026-08-15T05:59:00.445Z", "dateUpdated": "2026-10-16T18:55:36.724Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-17T05:46:34.280Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix flex array size in struct nvme_ns_head\n\nstruct nvme_ns_head contains a flexible array member, current_path[],\nwhich is indexed using the NUMA node ID:\nhead->current_path[numa_node_id()]\n\nThe structure is currently allocated as:\nsize = sizeof(struct nvme_ns_head) +\n (num_possible_nodes() * sizeof(struct nvme_ns *));\nhead = kzalloc(size, GFP_KERNEL);\n\nThis allocation assumes that NUMA node IDs are sequential and densely\npacked from 0 .. num_possible_nodes() - 1. While this assumption holds\non many systems, it is not always true on some architectures such as\npowerpc.\n\nOn some powerpc systems, NUMA node IDs can be sparse. For example:\nNUMA:\n NUMA node(s): 6\n NUMA node0 CPU(s): 80-159\n NUMA node8 CPU(s): 0-79\n NUMA node252 CPU(s):\n NUMA node253 CPU(s):\n NUMA node254 CPU(s):\n NUMA node255 CPU(s):\n\nThat is, the possible/online NUMA node IDs are: 0, 8, 252, 253, 254, 255\nIn this case: num_possible_nodes() = 6\n\nSo memory is allocated for only 6 entries in current_path[]. However,\nthe array is later indexed using the actual NUMA node ID. As a result,\naccesses such as:\nhead->current_path[8] or\nhead->current_path[252]\ngoes out of bounds, leading to the following KASAN splat:\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]\nWrite of size 8 at addr c00020003bda35b8 by task kworker/u641:2/1997\n\nCPU: 1 UID: 0 PID: 1997 Comm: kworker/u641:2 Not tainted 7.1.0-rc5-dirty #14 PREEMPT(lazy)\nHardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV\nWorkqueue: async async_run_entry_fn\nCall Trace:\n[c000200037fa7510] [c0000000021c23d4] dump_stack_lvl+0x88/0xdc (unreliable)\n[c000200037fa7540] [c0000000009fda90] print_report+0x22c/0x67c\n[c000200037fa7630] [c0000000009fd508] kasan_report+0x108/0x220\n[c000200037fa7740] [c0000000009fff48] __asan_store8+0xe8/0x120\n[c000200037fa7760] [c008000018e76474] nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]\n[c000200037fa7800] [c008000018e6556c] nvme_update_ns_info+0x4a4/0x5e0 [nvme_core]\n[c000200037fa7a50] [c008000018e66270] nvme_alloc_ns+0x6d8/0x1a70 [nvme_core]\n[c000200037fa7c20] [c008000018e679fc] nvme_scan_ns+0x3f4/0x630 [nvme_core]\n[c000200037fa7d10] [c00000000031f22c] async_run_entry_fn+0x9c/0x3a0\n[c000200037fa7db0] [c0000000002fa544] process_one_work+0x414/0xa10\n[c000200037fa7ec0] [c0000000002fbf00] worker_thread+0x320/0x640\n[c000200037fa7f80] [c00000000030d0f8] kthread+0x278/0x290\n[c000200037fa7fe0] [c00000000000ded8] start_kernel_thread+0x14/0x18\n\nAllocated by task 1997 on cpu 1 at 35.928317s:\n\nThe buggy address belongs to the object at c00020003bda3000\n which belongs to the cache kmalloc-rnd-15-2k of size 2048\nThe buggy address is located 16 bytes to the right of\n allocated 1448-byte region [c00020003bda3000, c00020003bda35a8)\n\nThe buggy address belongs to the physical page:\n\nMemory state around the buggy address:\n c00020003bda3480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n c00020003bda3500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n>c00020003bda3580: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc\n ^\n c00020003bda3600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n c00020003bda3680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n==================================================================\n\nFix this by allocating the flexible array using nr_node_ids instead\nof num_possible_nodes(). Since nr_node_ids represents the maximum\npossible NUMA node IDs, indexing current_path[] using numa_node_id()\nbecomes safe even on systems with sparse node IDs."}], "metrics": [{"cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "baseScore": 9.8, "baseSeverity": "CRITICAL"}, "scenarios": [{"lang": "en", "value": "AV:N - On IBM POWER cloud/enterprise hosts using NVMe-oF (TCP/RDMA/FC), a remote attacker on the storage fabric can deliver NVMe async namespace-changed completions that queue namespace rescans, driving nvme_scan_ns()\u2192nvme_alloc_ns()\u2192nvme_update_ns_info()\u2192nvme_mpath_revalidate_paths() over the network-facing NVMe host transport.\nAC:L - Once CONFIG_NVME_MULTIPATH is enabled on POWER systems with sparse NUMA IDs (e.g., nodes 0,8,252-255), indexing current_path[numa_node_id()] deterministically exceeds the num_possible_nodes()-sized allocation during boot scan, admin rescan, or multipath I/O without races or layout luck.\nPR:N - Triggering the bug via remote NVMe async events or normal multipath block I/O requires no local account, CAP_SYS_ADMIN, or other host privileges; only an existing NVMe attachment (local PCIe or preconfigured fabric) on a vulnerable POWER NUMA topology.\nUI:N - No victim user action is required beyond routine system operation such as boot-time namespace discovery, background kworker rescans, or ordinary storage I/O on multipathed NVMe namespaces.\nS:U - The out-of-bounds slab write corrupts host kernel heap memory in the NVMe multipath driver, enabling kernel privilege escalation within the same security authority rather than crossing VM, container, or IOMMU boundaries.\nC:H - KASAN reports an 8-byte slab-out-of-bounds write past the nvme_ns_head allocation; this heap corruption can overwrite adjacent kmalloc objects and be developed into arbitrary kernel memory disclosure primitives.\nI:H - The unchecked current_path[] index allows attacker-influenced 8-byte pointer writes beyond the allocation boundary, providing a heap corruption primitive suitable for arbitrary kernel writes and potential code execution.\nA:H - The confirmed slab-out-of-bounds write in nvme_mpath_revalidate_paths() can oops/panic the kernel during namespace scan or multipath I/O on affected POWER servers, causing complete node unavailability."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/nvme/host/core.c"], "versions": [{"version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "7e7b167e65610dfa7564d449474f4b477f9d4c1c", "status": "affected", "versionType": "git"}, {"version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "316b5f1168264844aa125959de1d6da2b1905795", "status": "affected", "versionType": "git"}, {"version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "1d4131b5c9823c7d2c86389898ad1b466af7df5e", "status": "affected", "versionType": "git"}, {"version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5", "status": "affected", "versionType": "git"}, {"version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6", "status": "affected", "versionType": "git"}, {"version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "140d6fff4ed266592492a23444043842b4af7a62", "status": "affected", "versionType": "git"}, {"version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "7173a741fed73de6247384056fe92e582ba12507", "status": "affected", "versionType": "git"}, {"version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "001e57554de81aa79c25c18fd53911d8a415c304", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/nvme/host/core.c"], "versions": [{"version": "4.20", "status": "affected"}, {"version": "0", "lessThan": "4.20", "status": "unaffected", "versionType": "semver"}, {"version": "5.10.261", "lessThanOrEqual": "5.10.*", "status": "unaffected", "versionType": "semver"}, {"version": "5.15.212", "lessThanOrEqual": "5.15.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.1.178", "lessThanOrEqual": "6.1.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.6.145", "lessThanOrEqual": "6.6.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.12.97", "lessThanOrEqual": "6.12.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.18.40", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.1.5", "lessThanOrEqual": "7.1.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.2", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.20", "versionEndExcluding": "5.10.261"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.20", "versionEndExcluding": "5.15.212"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.20", "versionEndExcluding": "6.1.178"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.20", "versionEndExcluding": "6.6.145"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.20", "versionEndExcluding": "6.12.97"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.20", "versionEndExcluding": "6.18.40"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.20", "versionEndExcluding": "7.1.5"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.20", "versionEndExcluding": "7.2"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/7e7b167e65610dfa7564d449474f4b477f9d4c1c"}, {"url": "https://git.kernel.org/stable/c/316b5f1168264844aa125959de1d6da2b1905795"}, {"url": "https://git.kernel.org/stable/c/1d4131b5c9823c7d2c86389898ad1b466af7df5e"}, {"url": "https://git.kernel.org/stable/c/9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5"}, {"url": "https://git.kernel.org/stable/c/bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6"}, {"url": "https://git.kernel.org/stable/c/140d6fff4ed266592492a23444043842b4af7a62"}, {"url": "https://git.kernel.org/stable/c/7173a741fed73de6247384056fe92e582ba12507"}, {"url": "https://git.kernel.org/stable/c/001e57554de81aa79c25c18fd53911d8a415c304"}], "title": "nvme-multipath: fix flex array size in struct nvme_ns_head", "x_generator": {"engine": "bippy-1.2.0"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-74384", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-10-16T18:54:58.881656Z"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-16T18:55:36.724Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-74384", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-10-16T18:54:58.881656Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-16T18:54:59.506Z"}}], "cna": {"title": "nvme-multipath: fix flex array size in struct nvme_ns_head", "metrics": [{"cvssV3_1": {"version": "3.1", "baseScore": 9.8, "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}, "scenarios": [{"lang": "en", "value": "AV:N - On IBM POWER cloud/enterprise hosts using NVMe-oF (TCP/RDMA/FC), a remote attacker on the storage fabric can deliver NVMe async namespace-changed completions that queue namespace rescans, driving nvme_scan_ns()\u2192nvme_alloc_ns()\u2192nvme_update_ns_info()\u2192nvme_mpath_revalidate_paths() over the network-facing NVMe host transport.\nAC:L - Once CONFIG_NVME_MULTIPATH is enabled on POWER systems with sparse NUMA IDs (e.g., nodes 0,8,252-255), indexing current_path[numa_node_id()] deterministically exceeds the num_possible_nodes()-sized allocation during boot scan, admin rescan, or multipath I/O without races or layout luck.\nPR:N - Triggering the bug via remote NVMe async events or normal multipath block I/O requires no local account, CAP_SYS_ADMIN, or other host privileges; only an existing NVMe attachment (local PCIe or preconfigured fabric) on a vulnerable POWER NUMA topology.\nUI:N - No victim user action is required beyond routine system operation such as boot-time namespace discovery, background kworker rescans, or ordinary storage I/O on multipathed NVMe namespaces.\nS:U - The out-of-bounds slab write corrupts host kernel heap memory in the NVMe multipath driver, enabling kernel privilege escalation within the same security authority rather than crossing VM, container, or IOMMU boundaries.\nC:H - KASAN reports an 8-byte slab-out-of-bounds write past the nvme_ns_head allocation; this heap corruption can overwrite adjacent kmalloc objects and be developed into arbitrary kernel memory disclosure primitives.\nI:H - The unchecked current_path[] index allows attacker-influenced 8-byte pointer writes beyond the allocation boundary, providing a heap corruption primitive suitable for arbitrary kernel writes and potential code execution.\nA:H - The confirmed slab-out-of-bounds write in nvme_mpath_revalidate_paths() can oops/panic the kernel during namespace scan or multipath I/O on affected POWER servers, causing complete node unavailability."}]}], "affected": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "7e7b167e65610dfa7564d449474f4b477f9d4c1c", "versionType": "git"}, {"status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "316b5f1168264844aa125959de1d6da2b1905795", "versionType": "git"}, {"status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "1d4131b5c9823c7d2c86389898ad1b466af7df5e", "versionType": "git"}, {"status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5", "versionType": "git"}, {"status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6", "versionType": "git"}, {"status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "140d6fff4ed266592492a23444043842b4af7a62", "versionType": "git"}, {"status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "7173a741fed73de6247384056fe92e582ba12507", "versionType": "git"}, {"status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "lessThan": "001e57554de81aa79c25c18fd53911d8a415c304", "versionType": "git"}], "programFiles": ["drivers/nvme/host/core.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "4.20"}, {"status": "unaffected", "version": "0", "lessThan": "4.20", "versionType": "semver"}, {"status": "unaffected", "version": "5.10.261", "versionType": "semver", "lessThanOrEqual": "5.10.*"}, {"status": "unaffected", "version": "5.15.212", "versionType": "semver", "lessThanOrEqual": "5.15.*"}, {"status": "unaffected", "version": "6.1.178", "versionType": "semver", "lessThanOrEqual": "6.1.*"}, {"status": "unaffected", "version": "6.6.145", "versionType": "semver", "lessThanOrEqual": "6.6.*"}, {"status": "unaffected", "version": "6.12.97", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.40", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.1.5", "versionType": "semver", "lessThanOrEqual": "7.1.*"}, {"status": "unaffected", "version": "7.2", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/nvme/host/core.c"], "defaultStatus": "affected"}], "references": [{"url": "https://git.kernel.org/stable/c/7e7b167e65610dfa7564d449474f4b477f9d4c1c"}, {"url": "https://git.kernel.org/stable/c/316b5f1168264844aa125959de1d6da2b1905795"}, {"url": "https://git.kernel.org/stable/c/1d4131b5c9823c7d2c86389898ad1b466af7df5e"}, {"url": "https://git.kernel.org/stable/c/9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5"}, {"url": "https://git.kernel.org/stable/c/bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6"}, {"url": "https://git.kernel.org/stable/c/140d6fff4ed266592492a23444043842b4af7a62"}, {"url": "https://git.kernel.org/stable/c/7173a741fed73de6247384056fe92e582ba12507"}, {"url": "https://git.kernel.org/stable/c/001e57554de81aa79c25c18fd53911d8a415c304"}], "x_generator": {"engine": "bippy-1.2.0"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix flex array size in struct nvme_ns_head\n\nstruct nvme_ns_head contains a flexible array member, current_path[],\nwhich is indexed using the NUMA node ID:\nhead->current_path[numa_node_id()]\n\nThe structure is currently allocated as:\nsize = sizeof(struct nvme_ns_head) +\n (num_possible_nodes() * sizeof(struct nvme_ns *));\nhead = kzalloc(size, GFP_KERNEL);\n\nThis allocation assumes that NUMA node IDs are sequential and densely\npacked from 0 .. num_possible_nodes() - 1. While this assumption holds\non many systems, it is not always true on some architectures such as\npowerpc.\n\nOn some powerpc systems, NUMA node IDs can be sparse. For example:\nNUMA:\n NUMA node(s): 6\n NUMA node0 CPU(s): 80-159\n NUMA node8 CPU(s): 0-79\n NUMA node252 CPU(s):\n NUMA node253 CPU(s):\n NUMA node254 CPU(s):\n NUMA node255 CPU(s):\n\nThat is, the possible/online NUMA node IDs are: 0, 8, 252, 253, 254, 255\nIn this case: num_possible_nodes() = 6\n\nSo memory is allocated for only 6 entries in current_path[]. However,\nthe array is later indexed using the actual NUMA node ID. As a result,\naccesses such as:\nhead->current_path[8] or\nhead->current_path[252]\ngoes out of bounds, leading to the following KASAN splat:\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]\nWrite of size 8 at addr c00020003bda35b8 by task kworker/u641:2/1997\n\nCPU: 1 UID: 0 PID: 1997 Comm: kworker/u641:2 Not tainted 7.1.0-rc5-dirty #14 PREEMPT(lazy)\nHardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV\nWorkqueue: async async_run_entry_fn\nCall Trace:\n[c000200037fa7510] [c0000000021c23d4] dump_stack_lvl+0x88/0xdc (unreliable)\n[c000200037fa7540] [c0000000009fda90] print_report+0x22c/0x67c\n[c000200037fa7630] [c0000000009fd508] kasan_report+0x108/0x220\n[c000200037fa7740] [c0000000009fff48] __asan_store8+0xe8/0x120\n[c000200037fa7760] [c008000018e76474] nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]\n[c000200037fa7800] [c008000018e6556c] nvme_update_ns_info+0x4a4/0x5e0 [nvme_core]\n[c000200037fa7a50] [c008000018e66270] nvme_alloc_ns+0x6d8/0x1a70 [nvme_core]\n[c000200037fa7c20] [c008000018e679fc] nvme_scan_ns+0x3f4/0x630 [nvme_core]\n[c000200037fa7d10] [c00000000031f22c] async_run_entry_fn+0x9c/0x3a0\n[c000200037fa7db0] [c0000000002fa544] process_one_work+0x414/0xa10\n[c000200037fa7ec0] [c0000000002fbf00] worker_thread+0x320/0x640\n[c000200037fa7f80] [c00000000030d0f8] kthread+0x278/0x290\n[c000200037fa7fe0] [c00000000000ded8] start_kernel_thread+0x14/0x18\n\nAllocated by task 1997 on cpu 1 at 35.928317s:\n\nThe buggy address belongs to the object at c00020003bda3000\n which belongs to the cache kmalloc-rnd-15-2k of size 2048\nThe buggy address is located 16 bytes to the right of\n allocated 1448-byte region [c00020003bda3000, c00020003bda35a8)\n\nThe buggy address belongs to the physical page:\n\nMemory state around the buggy address:\n c00020003bda3480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n c00020003bda3500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n>c00020003bda3580: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc\n ^\n c00020003bda3600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n c00020003bda3680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n==================================================================\n\nFix this by allocating the flexible array using nr_node_ids instead\nof num_possible_nodes(). Since nr_node_ids represents the maximum\npossible NUMA node IDs, indexing current_path[] using numa_node_id()\nbecomes safe even on systems with sparse node IDs."}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "5.10.261", "versionStartIncluding": "4.20"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "5.15.212", "versionStartIncluding": "4.20"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.1.178", "versionStartIncluding": "4.20"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.6.145", "versionStartIncluding": "4.20"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.12.97", "versionStartIncluding": "4.20"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.18.40", "versionStartIncluding": "4.20"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "7.1.5", "versionStartIncluding": "4.20"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "7.2", "versionStartIncluding": "4.20"}], "operator": "OR"}]}], "providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-17T05:46:34.280Z"}}}, "cveMetadata": {"cveId": "CVE-2026-74384", "state": "PUBLISHED", "dateUpdated": "2026-10-16T18:55:36.724Z", "dateReserved": "2026-08-15T05:44:03.890Z", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "datePublished": "2026-08-15T05:59:00.445Z", "assignerShortName": "Linux"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["drivers/nvme/host/core.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "7e7b167e65610dfa7564d449474f4b477f9d4c1c", "status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "versionType": "git"}, {"lessThan": "316b5f1168264844aa125959de1d6da2b1905795", "status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "versionType": "git"}, {"lessThan": "1d4131b5c9823c7d2c86389898ad1b466af7df5e", "status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "versionType": "git"}, {"lessThan": "9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5", "status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "versionType": "git"}, {"lessThan": "bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6", "status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "versionType": "git"}, {"lessThan": "140d6fff4ed266592492a23444043842b4af7a62", "status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "versionType": "git"}, {"lessThan": "7173a741fed73de6247384056fe92e582ba12507", "status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "versionType": "git"}, {"lessThan": "001e57554de81aa79c25c18fd53911d8a415c304", "status": "affected", "version": "f333444708f82c4a4d3ccac004da0bfd9cfdfa42", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["drivers/nvme/host/core.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "4.20"}, {"lessThan": "4.20", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "5.10.*", "status": "unaffected", "version": "5.10.261", "versionType": "semver"}, {"lessThanOrEqual": "5.15.*", "status": "unaffected", "version": "5.15.212", "versionType": "semver"}, {"lessThanOrEqual": "6.1.*", "status": "unaffected", "version": "6.1.178", "versionType": "semver"}, {"lessThanOrEqual": "6.6.*", "status": "unaffected", "version": "6.6.145", "versionType": "semver"}, {"lessThanOrEqual": "6.12.*", "status": "unaffected", "version": "6.12.97", "versionType": "semver"}, {"lessThanOrEqual": "6.18.*", "status": "unaffected", "version": "6.18.40", "versionType": "semver"}, {"lessThanOrEqual": "7.1.*", "status": "unaffected", "version": "7.1.5", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "7.2", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix flex array size in struct nvme_ns_head\n\nstruct nvme_ns_head contains a flexible array member, current_path[],\nwhich is indexed using the NUMA node ID:\nhead->current_path[numa_node_id()]\n\nThe structure is currently allocated as:\nsize = sizeof(struct nvme_ns_head) +\n (num_possible_nodes() * sizeof(struct nvme_ns *));\nhead = kzalloc(size, GFP_KERNEL);\n\nThis allocation assumes that NUMA node IDs are sequential and densely\npacked from 0 .. num_possible_nodes() - 1. While this assumption holds\non many systems, it is not always true on some architectures such as\npowerpc.\n\nOn some powerpc systems, NUMA node IDs can be sparse. For example:\nNUMA:\n NUMA node(s): 6\n NUMA node0 CPU(s): 80-159\n NUMA node8 CPU(s): 0-79\n NUMA node252 CPU(s):\n NUMA node253 CPU(s):\n NUMA node254 CPU(s):\n NUMA node255 CPU(s):\n\nThat is, the possible/online NUMA node IDs are: 0, 8, 252, 253, 254, 255\nIn this case: num_possible_nodes() = 6\n\nSo memory is allocated for only 6 entries in current_path[]. However,\nthe array is later indexed using the actual NUMA node ID. As a result,\naccesses such as:\nhead->current_path[8] or\nhead->current_path[252]\ngoes out of bounds, leading to the following KASAN splat:\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]\nWrite of size 8 at addr c00020003bda35b8 by task kworker/u641:2/1997\n\nCPU: 1 UID: 0 PID: 1997 Comm: kworker/u641:2 Not tainted 7.1.0-rc5-dirty #14 PREEMPT(lazy)\nHardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV\nWorkqueue: async async_run_entry_fn\nCall Trace:\n[c000200037fa7510] [c0000000021c23d4] dump_stack_lvl+0x88/0xdc (unreliable)\n[c000200037fa7540] [c0000000009fda90] print_report+0x22c/0x67c\n[c000200037fa7630] [c0000000009fd508] kasan_report+0x108/0x220\n[c000200037fa7740] [c0000000009fff48] __asan_store8+0xe8/0x120\n[c000200037fa7760] [c008000018e76474] nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]\n[c000200037fa7800] [c008000018e6556c] nvme_update_ns_info+0x4a4/0x5e0 [nvme_core]\n[c000200037fa7a50] [c008000018e66270] nvme_alloc_ns+0x6d8/0x1a70 [nvme_core]\n[c000200037fa7c20] [c008000018e679fc] nvme_scan_ns+0x3f4/0x630 [nvme_core]\n[c000200037fa7d10] [c00000000031f22c] async_run_entry_fn+0x9c/0x3a0\n[c000200037fa7db0] [c0000000002fa544] process_one_work+0x414/0xa10\n[c000200037fa7ec0] [c0000000002fbf00] worker_thread+0x320/0x640\n[c000200037fa7f80] [c00000000030d0f8] kthread+0x278/0x290\n[c000200037fa7fe0] [c00000000000ded8] start_kernel_thread+0x14/0x18\n\nAllocated by task 1997 on cpu 1 at 35.928317s:\n\nThe buggy address belongs to the object at c00020003bda3000\n which belongs to the cache kmalloc-rnd-15-2k of size 2048\nThe buggy address is located 16 bytes to the right of\n allocated 1448-byte region [c00020003bda3000, c00020003bda35a8)\n\nThe buggy address belongs to the physical page:\n\nMemory state around the buggy address:\n c00020003bda3480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n c00020003bda3500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n>c00020003bda3580: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc\n ^\n c00020003bda3600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n c00020003bda3680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n==================================================================\n\nFix this by allocating the flexible array using nr_node_ids instead\nof num_possible_nodes(). Since nr_node_ids represents the maximum\npossible NUMA node IDs, indexing current_path[] using numa_node_id()\nbecomes safe even on systems with sparse node IDs."}], "id": "CVE-2026-74384", "lastModified": "2026-10-16T19:17:43.143", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 9.8, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 5.9, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-74384", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-10-16T18:54:58.881656Z", "version": "2.0.3"}}]}, "published": "2026-08-15T06:22:40.270", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/001e57554de81aa79c25c18fd53911d8a415c304"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/140d6fff4ed266592492a23444043842b4af7a62"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/1d4131b5c9823c7d2c86389898ad1b466af7df5e"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/316b5f1168264844aa125959de1d6da2b1905795"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/7173a741fed73de6247384056fe92e582ba12507"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/7e7b167e65610dfa7564d449474f4b477f9d4c1c"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: nvme-multipath: fix flex array size in struct nvme_ns_head", "id": "2516815", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2516815"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "cwe": "CWE-787", "details": ["In the Linux kernel, the following vulnerability has been resolved:\nnvme-multipath: fix flex array size in struct nvme_ns_head\nstruct nvme_ns_head contains a flexible array member, current_path[],\nwhich is indexed using the NUMA node ID:\nhead->current_path[numa_node_id()]\nThe structure is currently allocated as:\nsize = sizeof(struct nvme_ns_head) +\n(num_possible_nodes() * sizeof(struct nvme_ns *));\nhead = kzalloc(size, GFP_KERNEL);\nThis allocation assumes that NUMA node IDs are sequential and densely\npacked from 0 .. num_possible_nodes() - 1. While this assumption holds\non many systems, it is not always true on some architectures such as\npowerpc.\nOn some powerpc systems, NUMA node IDs can be sparse. For example:\nNUMA:\nNUMA node(s): 6\nNUMA node0 CPU(s): 80-159\nNUMA node8 CPU(s): 0-79\nNUMA node252 CPU(s):\nNUMA node253 CPU(s):\nNUMA node254 CPU(s):\nNUMA node255 CPU(s):\nThat is, the possible/online NUMA node IDs are: 0, 8, 252, 253, 254, 255\nIn this case: num_possible_nodes() = 6\nSo memory is allocated for only 6 entries in current_path[]. However,\nthe array is later indexed using the actual NUMA node ID. As a result,\naccesses such as:\nhead->current_path[8] or\nhead->current_path[252]\ngoes out of bounds, leading to the following KASAN splat:\n==================================================================\nBUG: KASAN: slab-out-of-bounds in nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]\nWrite of size 8 at addr c00020003bda35b8 by task kworker/u641:2/1997\nCPU: 1 UID: 0 PID: 1997 Comm: kworker/u641:2 Not tainted 7.1.0-rc5-dirty #14 PREEMPT(lazy)\nHardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV\nWorkqueue: async async_run_entry_fn\nCall Trace:\n[c000200037fa7510] [c0000000021c23d4] dump_stack_lvl+0x88/0xdc (unreliable)\n[c000200037fa7540] [c0000000009fda90] print_report+0x22c/0x67c\n[c000200037fa7630] [c0000000009fd508] kasan_report+0x108/0x220\n[c000200037fa7740] [c0000000009fff48] __asan_store8+0xe8/0x120\n[c000200037fa7760] [c008000018e76474] nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core]\n[c000200037fa7800] [c008000018e6556c] nvme_update_ns_info+0x4a4/0x5e0 [nvme_core]\n[c000200037fa7a50] [c008000018e66270] nvme_alloc_ns+0x6d8/0x1a70 [nvme_core]\n[c000200037fa7c20] [c008000018e679fc] nvme_scan_ns+0x3f4/0x630 [nvme_core]\n[c000200037fa7d10] [c00000000031f22c] async_run_entry_fn+0x9c/0x3a0\n[c000200037fa7db0] [c0000000002fa544] process_one_work+0x414/0xa10\n[c000200037fa7ec0] [c0000000002fbf00] worker_thread+0x320/0x640\n[c000200037fa7f80] [c00000000030d0f8] kthread+0x278/0x290\n[c000200037fa7fe0] [c00000000000ded8] start_kernel_thread+0x14/0x18\nAllocated by task 1997 on cpu 1 at 35.928317s:\nThe buggy address belongs to the object at c00020003bda3000\nwhich belongs to the cache kmalloc-rnd-15-2k of size 2048\nThe buggy address is located 16 bytes to the right of\nallocated 1448-byte region [c00020003bda3000, c00020003bda35a8)\nThe buggy address belongs to the physical page:\nMemory state around the buggy address:\nc00020003bda3480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\nc00020003bda3500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n>c00020003bda3580: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc\n^\nc00020003bda3600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\nc00020003bda3680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n==================================================================\nFix this by allocating the flexible array using nr_node_ids instead\nof num_possible_nodes(). Since nr_node_ids represents the maximum\npossible NUMA node IDs, indexing current_path[] using numa_node_id()\nbecomes safe even on systems with sparse node IDs.", "A flaw was found in the Linux kernel's nvme-multipath component. This vulnerability arises from an incorrect calculation of a flexible array size, current_path[], which is indexed using Non-Uniform Memory Access (NUMA) node IDs. On certain architectures, such as powerpc, NUMA node IDs can be sparse, leading to out-of-bounds memory access when the array is indexed. This out-of-bounds write can cause a system crash, resulting in a Denial of Service (DoS)."], "name": "CVE-2026-74384", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Fix deferred", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2026-08-15T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-74384\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-74384\nhttps://lore.kernel.org/linux-cve-announce/2026081505-CVE-2026-74384-f743@gregkh/T"], "threat_severity": "Moderate"}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[f333444708f82c4a4d3ccac004da0bfd9cfdfa42,7e7b167e65610dfa7564d449474f4b477f9d4c1c)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[f333444708f82c4a4d3ccac004da0bfd9cfdfa42,316b5f1168264844aa125959de1d6da2b1905795)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[f333444708f82c4a4d3ccac004da0bfd9cfdfa42,1d4131b5c9823c7d2c86389898ad1b466af7df5e)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[f333444708f82c4a4d3ccac004da0bfd9cfdfa42,9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[f333444708f82c4a4d3ccac004da0bfd9cfdfa42,bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[f333444708f82c4a4d3ccac004da0bfd9cfdfa42,140d6fff4ed266592492a23444043842b4af7a62)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[f333444708f82c4a4d3ccac004da0bfd9cfdfa42,7173a741fed73de6247384056fe92e582ba12507)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[f333444708f82c4a4d3ccac004da0bfd9cfdfa42,001e57554de81aa79c25c18fd53911d8a415c304)"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}, {"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "4.20"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[0,4.20)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[5.10.261,6.0.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[5.15.212,6.0.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[6.1.178,7.0.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[6.6.145,7.0.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[6.12.97,7.0.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[6.18.40,7.0.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[7.1.5,8.0.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "generic", "value": "[7.2-rc1,*]"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}], "created": "2026-08-15T13:30:04.657650+00:00", "updated": "2026-08-22T02:00:17.909587+00:00", "vendors": ["linux", "linux$PRODUCT$linux_kernel"]}