GHSA-VFHR-8GQ2-GPCV
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-14 15:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-80963"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:02Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm-stats: fix a crash if allocation of per-cpu data fails\n\nIf \"dm_kvzalloc(percpu_alloc_size, cpu_to_node(cpu))\" fails, the code\njumps to the \"out\" label and calls dm_stat_free. dm_stat_free does\n\"for_each_possible_cpu(cpu) { dm_kvfree(s-\u003estat_percpu[cpu][0].histogram,\ns-\u003ehistogram_alloc_size);\", which crashes with NULL pointer dereference\nif s-\u003estat_percpu[cpu] is NULL.\n\nThis commit fixes the bug by testing s-\u003estat_percpu[cpu] for NULL before\nusing it.",
"id": "GHSA-vfhr-8gq2-gpcv",
"modified": "2026-09-14T15:32:20Z",
"published": "2026-09-11T21:31:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80963"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0c8f7870ed3ebd512f090d7714cc2c556b9e5c75"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/389a50d094e13724f5f45e6d9d6ef734c98ba291"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/564d17573ef643c13cf6e9015124a205fa65e704"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/74210fa072960a18bb0eead487585452af722e4f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9805d87d0e26c68ee69da3928e665214d2e2851a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c3f211b7a277dd404b4e7d23095be964b5b46a27"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cc87e26d9cce22061dc21e51e11afef29dbbc36a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e45f0b0c41139810ff395ba2f3cfca1460a5b8a6"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.