CVE-2026-97905
CVE CVE-2026-97905EUVD EUVD-2026-86759Published 2026-09-25T10:22:31.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: cpufreq: zero-initialize policy cpumask before sysfs publication cpufreq_policy_alloc() allocates policy->cpus with alloc_cpumask_var(), i.e. without __GFP_ZERO, unlike the sibling related_cpus and real_cpus masks. With CONFIG_CPUMASK_OFFSTACK=y the mask is a separate kmalloc_node() allocation, so its bitmap holds whatever the slab allocator left behind: cpufreq_online() cpufreq_policy_alloc() alloc_cpumask_var(&policy->cpus) /* bitmap is uninitialized */ kobject_init_and_add() /* policy%u/ appears in sysfs */ cpufreq_policy_online() cpumask_copy(policy->cpus, cpumask_of(cpu)) /* first valid value */ This leaves a window in which the sysfs attributes are already reachable while policy->cpus is still garbage. show()/store() gate on policy_is_inactive(), i.e. cpumask_empty(policy->cpus), so a non-zero bitmap makes them run the attribute callbacks on a policy that is not initialized yet. Fix this by using zalloc_cpumask_var() for policy->cpus.
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 2fc3384dc75bf7333384c7a16d12c796f61c3f56 <bbc0472d2270bf732142ca71579d6ede636174ed; patch: 7.2.7; 4.2; patch: 6.12.111; patch: 0; 2fc3384dc75bf7333384c7a16d12c796f61c3f56 <0de2f3918fbbbb767e7e716178194b66560dd12a; 2fc3384dc75bf7333384c7a16d12c796f61c3f56 <6e166b9281dec98aed19213a84235250e5fdb081; patch: 6.18.53; patch: 7.3-rc3; 2fc3384dc75bf7333384c7a16d12c796f61c3f56 <54d37bcf2f497140b9207968557ddb484058e749
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.