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-80963dm-stats: fix a crash if allocation of per-cpu data fails

Description

In the Linux kernel, the following vulnerability has been resolved: dm-stats: fix a crash if allocation of per-cpu data fails If "dm_kvzalloc(percpu_alloc_size, cpu_to_node(cpu))" fails, the code jumps to the "out" label and calls dm_stat_free. dm_stat_free does "for_each_possible_cpu(cpu) { dm_kvfree(s->stat_percpu[cpu][0].histogram, s->histogram_alloc_size);", which crashes with NULL pointer dereference if s->stat_percpu[cpu] is NULL. This commit fixes the bug by testing s->stat_percpu[cpu] for NULL before using it.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 38 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.18% · top 93% of all CVEs (17 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 fd2ed4d252701d3bbed4cd3e3d267ad469bb832a – < e45f0b0c41139810ff395ba2f3cfca1460a5b8a6
    • affected fd2ed4d252701d3bbed4cd3e3d267ad469bb832a – < 9805d87d0e26c68ee69da3928e665214d2e2851a
    • affected fd2ed4d252701d3bbed4cd3e3d267ad469bb832a – < 564d17573ef643c13cf6e9015124a205fa65e704
    • affected fd2ed4d252701d3bbed4cd3e3d267ad469bb832a – < 389a50d094e13724f5f45e6d9d6ef734c98ba291
    • affected fd2ed4d252701d3bbed4cd3e3d267ad469bb832a – < c3f211b7a277dd404b4e7d23095be964b5b46a27
    • affected fd2ed4d252701d3bbed4cd3e3d267ad469bb832a – < 74210fa072960a18bb0eead487585452af722e4f
    • affected fd2ed4d252701d3bbed4cd3e3d267ad469bb832a – < 0c8f7870ed3ebd512f090d7714cc2c556b9e5c75
    • affected fd2ed4d252701d3bbed4cd3e3d267ad469bb832a – < cc87e26d9cce22061dc21e51e11afef29dbbc36a
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .