CVE-2026-97905

cpufreq: zero-initialize policy cpumask before sysfs publication

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.

Key facts

Published
25 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.216% likely to be exploited in the next 30 days, higher than 12.153% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 2fc3384dc75bf7333384c7a16d12c796f61c3f56 up to but excluding e13370c5b549712f49f80234df249303381c53b4 (affected)
  • 2fc3384dc75bf7333384c7a16d12c796f61c3f56 up to but excluding e807920031ca32b668f9e7a1efbd21858f03d64b (affected)
  • 2fc3384dc75bf7333384c7a16d12c796f61c3f56 up to but excluding ca52482508b3ac9febe74ca4f732647d394727b8 (affected)
  • 2fc3384dc75bf7333384c7a16d12c796f61c3f56 up to but excluding 06f273d29e5e0fe5c775a65c563fbeed8cd94c7a (affected)
  • 2fc3384dc75bf7333384c7a16d12c796f61c3f56 up to but excluding 0de2f3918fbbbb767e7e716178194b66560dd12a (affected)
  • 2fc3384dc75bf7333384c7a16d12c796f61c3f56 up to but excluding 6e166b9281dec98aed19213a84235250e5fdb081 (affected)
  • 2fc3384dc75bf7333384c7a16d12c796f61c3f56 up to but excluding bbc0472d2270bf732142ca71579d6ede636174ed (affected)
  • 2fc3384dc75bf7333384c7a16d12c796f61c3f56 up to but excluding 54d37bcf2f497140b9207968557ddb484058e749 (affected)
LinuxLinux
  • Default status: affected
  • 4.2 (affected)
  • 0 up to but excluding 4.2 (unaffected)
  • 5.10.271 up to and including 5.10.* (unaffected)
  • 5.15.222 up to and including 5.15.* (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References