GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2026-74384 (GCVE-0-2026-74384)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:59 – Updated: 2026-08-17 05:46
VLAI
Title
nvme-multipath: fix flex array size in struct nvme_ns_head
Summary
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.
Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: f333444708f82c4a4d3ccac004da0bfd9cfdfa42 , < 7e7b167e65610dfa7564d449474f4b477f9d4c1c (git)
Affected: f333444708f82c4a4d3ccac004da0bfd9cfdfa42 , < 316b5f1168264844aa125959de1d6da2b1905795 (git)
Affected: f333444708f82c4a4d3ccac004da0bfd9cfdfa42 , < 1d4131b5c9823c7d2c86389898ad1b466af7df5e (git)
Affected: f333444708f82c4a4d3ccac004da0bfd9cfdfa42 , < 9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5 (git)
Affected: f333444708f82c4a4d3ccac004da0bfd9cfdfa42 , < bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6 (git)
Affected: f333444708f82c4a4d3ccac004da0bfd9cfdfa42 , < 140d6fff4ed266592492a23444043842b4af7a62 (git)
Affected: f333444708f82c4a4d3ccac004da0bfd9cfdfa42 , < 7173a741fed73de6247384056fe92e582ba12507 (git)
Affected: f333444708f82c4a4d3ccac004da0bfd9cfdfa42 , < 001e57554de81aa79c25c18fd53911d8a415c304 (git)
guessed Create a notification for this product.
Linux Linux Affected: 4.20
Unaffected: 0 , < 4.20 (semver)
Unaffected: 5.10.261 , ≤ 5.10.* (semver)
Unaffected: 5.15.212 , ≤ 5.15.* (semver)
Unaffected: 6.1.178 , ≤ 6.1.* (semver)
Unaffected: 6.6.145 , ≤ 6.6.* (semver)
Unaffected: 6.12.97 , ≤ 6.12.* (semver)
Unaffected: 6.18.40 , ≤ 6.18.* (semver)
Unaffected: 7.1.5 , ≤ 7.1.* (semver)
Unaffected: 7.2 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "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"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.261",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.212",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.178",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.145",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.97",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.40",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "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-\u003ecurrent_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-\u003ecurrent_path[8] or\nhead-\u003ecurrent_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\u003ec00020003bda3580: 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": {
            "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",
            "version": "3.1"
          },
          "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."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:46:34.280Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "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"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-74384",
    "datePublished": "2026-08-15T05:59:00.445Z",
    "dateReserved": "2026-08-15T05:44:03.890Z",
    "dateUpdated": "2026-08-17T05:46:34.280Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-74384",
      "date": "2026-09-03",
      "epss": "0.00514",
      "percentile": "0.41831"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-74384\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-08-15T06:22:40.270\",\"lastModified\":\"2026-08-17T06:19:33.300\",\"vulnStatus\":\"Received\",\"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-\u003ecurrent_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-\u003ecurrent_path[8] or\\nhead-\u003ecurrent_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\u003ec00020003bda3580: 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.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/nvme/host/core.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"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\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/nvme/host/core.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"4.20\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"4.20\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.10.261\",\"lessThanOrEqual\":\"5.10.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.212\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.1.178\",\"lessThanOrEqual\":\"6.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.145\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12.97\",\"lessThanOrEqual\":\"6.12.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18.40\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1.5\",\"lessThanOrEqual\":\"7.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.2\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"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\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":5.9}]},\"references\":[{\"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\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-20T20:53:40+00:00",
      "cve": "CVE-2026-74384",
      "id": "CVE-2026-74384",
      "initial_release_date": "2026-08-15T00:00:00+00:00",
      "product_status:known_affected": "232",
      "product_status:known_not_affected": "42",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: nvme-multipath: fix flex array size in struct nvme_ns_head",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-74384.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-29T01:08:27Z",
      "cve": "CVE-2026-74384",
      "id": "CVE-2026-74384",
      "initial_release_date": "2026-08-29T01:08:27Z",
      "product_status:known_affected": "356",
      "product_status:known_not_affected": "6",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-74384",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-74384.json",
      "version": "2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.