CVE-2026-80963
CVE CVE-2026-80963EUVD EUVD-2026-76286Published 2026-09-11T19:42:29.000ZLast changed 2026-09-14T11:59:09.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.2.4; patch: 5.10.270; 3.12; fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <389a50d094e13724f5f45e6d9d6ef734c98ba291; patch: 0; fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <74210fa072960a18bb0eead487585452af722e4f; patch: 6.18.50; fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <e45f0b0c41139810ff395ba2f3cfca1460a5b8a6; patch: 7.3-rc1; fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <c3f211b7a277dd404b4e7d23095be964b5b46a27; patch: 5.15.221; patch: 6.1.188; fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <cc87e26d9cce22061dc21e51e11afef29dbbc36a; fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <564d17573ef643c13cf6e9015124a205fa65e704; fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <9805d87d0e26c68ee69da3928e665214d2e2851a; patch: 6.6.157; fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <0c8f7870ed3ebd512f090d7714cc2c556b9e5c75; patch: 6.12.109
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.