Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93172mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug

Description

In the Linux kernel, the following vulnerability has been resolved: mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug We miss a failed allocation check for pgdat->per_cpu_nodestats, which results in a NULL deref when we offset into the per-cpu area. Propagate -ENOMEM up the stack and leave per_cpu_nodestats pointing at boot_nodestats so a later online can retry the allocation. hotadd_init_pgdat() returns NULL on failure, which __try_online_node() already maps to -ENOMEM. On failure nothing needs to be unwound: - the node is never marked online - per_cpu_nodestats is left pointing at boot_nodestats - __add_memory_resource() cleans up pending memblock resources - later online attempts retry the per_cpu_nodestats allocation

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 75ef7184053989118d3814c558a9af62e7376a58 – < eb872b92e26c2576742d541e45f28b50af059b8b
    • affected 75ef7184053989118d3814c558a9af62e7376a58 – < 4dda09e7ca0bf0c3fa7c5c8f134d9804b67f455c
    • affected 75ef7184053989118d3814c558a9af62e7376a58 – < 4cc5caef9a8d1894dfa31d84a0daa0ac1437dadc
    • affected 75ef7184053989118d3814c558a9af62e7376a58 – < bc3b5e6519b8df22d622a03eab6772784da97db4
    • affected 75ef7184053989118d3814c558a9af62e7376a58 – < 1017fe1c7f48e511c5a680e3057005daaff2f3a2
    • affected 75ef7184053989118d3814c558a9af62e7376a58 – < 2ebce860bdd7ae5e13002811bc9bbbf33fcfc221
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93172 badge
[![CVE-2026-93172](https://cveledger.app/badge/CVE-2026-93172.svg)](https://cveledger.app/cve/CVE-2026-93172)

Record last updated .