CVE-2026-97905cpufreq: zero-initialize policy cpumask before sysfs publication
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 24 days later
· 24 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.22% · top 88% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < e13370c5b549712f49f80234df249303381c53b4
- affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < e807920031ca32b668f9e7a1efbd21858f03d64b
- affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < ca52482508b3ac9febe74ca4f732647d394727b8
- affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < 06f273d29e5e0fe5c775a65c563fbeed8cd94c7a
- affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < 0de2f3918fbbbb767e7e716178194b66560dd12a
- affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < 6e166b9281dec98aed19213a84235250e5fdb081
- affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < bbc0472d2270bf732142ca71579d6ede636174ed
- affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 – < 54d37bcf2f497140b9207968557ddb484058e749
- affected 4.2
- unaffected < 4.2
- unaffected 5.10.271 – ≤ 5.10.*
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/e13370c5b549712f49f80234df249303381c53b4 (opens in a new tab)
- https://git.kernel.org/stable/c/e807920031ca32b668f9e7a1efbd21858f03d64b (opens in a new tab)
- https://git.kernel.org/stable/c/ca52482508b3ac9febe74ca4f732647d394727b8 (opens in a new tab)
- https://git.kernel.org/stable/c/06f273d29e5e0fe5c775a65c563fbeed8cd94c7a (opens in a new tab)
- https://git.kernel.org/stable/c/0de2f3918fbbbb767e7e716178194b66560dd12a (opens in a new tab)
- https://git.kernel.org/stable/c/6e166b9281dec98aed19213a84235250e5fdb081 (opens in a new tab)
- https://git.kernel.org/stable/c/bbc0472d2270bf732142ca71579d6ede636174ed (opens in a new tab)
- https://git.kernel.org/stable/c/54d37bcf2f497140b9207968557ddb484058e749 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86759 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97905)Record last updated .