{"api_version":"1","generated_at":"2026-10-02T03:44:40+00:00","cve":"CVE-2026-97905","urls":{"html":"https://cve.report/CVE-2026-97905","api":"https://cve.report/api/cve/CVE-2026-97905.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97905","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97905"},"summary":{"title":"cpufreq: zero-initialize policy cpumask before sysfs publication","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: zero-initialize policy cpumask before sysfs publication\n\ncpufreq_policy_alloc() allocates policy->cpus with alloc_cpumask_var(),\ni.e. without __GFP_ZERO, unlike the sibling related_cpus and real_cpus\nmasks. With CONFIG_CPUMASK_OFFSTACK=y the mask is a separate\nkmalloc_node() allocation, so its bitmap holds whatever the slab allocator\nleft behind:\n\n  cpufreq_online()\n    cpufreq_policy_alloc()\n      alloc_cpumask_var(&policy->cpus)    /* bitmap is uninitialized */\n      kobject_init_and_add()              /* policy%u/ appears in sysfs */\n    cpufreq_policy_online()\n      cpumask_copy(policy->cpus, cpumask_of(cpu))  /* first valid value */\n\nThis leaves a window in which the sysfs attributes are already reachable\nwhile policy->cpus is still garbage. show()/store() gate on\npolicy_is_inactive(), i.e. cpumask_empty(policy->cpus), so a non-zero\nbitmap makes them run the attribute callbacks on a policy that is not\ninitialized yet.\n\nFix this by using zalloc_cpumask_var() for policy->cpus.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:17","updated_at":"2026-09-25 11:17:17"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/54d37bcf2f497140b9207968557ddb484058e749","name":"https://git.kernel.org/stable/c/54d37bcf2f497140b9207968557ddb484058e749","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0de2f3918fbbbb767e7e716178194b66560dd12a","name":"https://git.kernel.org/stable/c/0de2f3918fbbbb767e7e716178194b66560dd12a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bbc0472d2270bf732142ca71579d6ede636174ed","name":"https://git.kernel.org/stable/c/bbc0472d2270bf732142ca71579d6ede636174ed","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/6e166b9281dec98aed19213a84235250e5fdb081","name":"https://git.kernel.org/stable/c/6e166b9281dec98aed19213a84235250e5fdb081","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97905","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97905","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 0de2f3918fbbbb767e7e716178194b66560dd12a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 6e166b9281dec98aed19213a84235250e5fdb081 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 bbc0472d2270bf732142ca71579d6ede636174ed git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2fc3384dc75bf7333384c7a16d12c796f61c3f56 54d37bcf2f497140b9207968557ddb484058e749 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.2","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.2 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"97905","cve":"CVE-2026-97905","epss":"0.002000000","percentile":"0.088150000","score_date":"2026-09-27","updated_at":"2026-09-28 00:02:24"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/cpufreq/cpufreq.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"0de2f3918fbbbb767e7e716178194b66560dd12a","status":"affected","version":"2fc3384dc75bf7333384c7a16d12c796f61c3f56","versionType":"git"},{"lessThan":"6e166b9281dec98aed19213a84235250e5fdb081","status":"affected","version":"2fc3384dc75bf7333384c7a16d12c796f61c3f56","versionType":"git"},{"lessThan":"bbc0472d2270bf732142ca71579d6ede636174ed","status":"affected","version":"2fc3384dc75bf7333384c7a16d12c796f61c3f56","versionType":"git"},{"lessThan":"54d37bcf2f497140b9207968557ddb484058e749","status":"affected","version":"2fc3384dc75bf7333384c7a16d12c796f61c3f56","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/cpufreq/cpufreq.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.2"},{"lessThan":"4.2","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"4.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"4.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"4.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc3","versionStartIncluding":"4.2","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: zero-initialize policy cpumask before sysfs publication\n\ncpufreq_policy_alloc() allocates policy->cpus with alloc_cpumask_var(),\ni.e. without __GFP_ZERO, unlike the sibling related_cpus and real_cpus\nmasks. With CONFIG_CPUMASK_OFFSTACK=y the mask is a separate\nkmalloc_node() allocation, so its bitmap holds whatever the slab allocator\nleft behind:\n\n  cpufreq_online()\n    cpufreq_policy_alloc()\n      alloc_cpumask_var(&policy->cpus)    /* bitmap is uninitialized */\n      kobject_init_and_add()              /* policy%u/ appears in sysfs */\n    cpufreq_policy_online()\n      cpumask_copy(policy->cpus, cpumask_of(cpu))  /* first valid value */\n\nThis leaves a window in which the sysfs attributes are already reachable\nwhile policy->cpus is still garbage. show()/store() gate on\npolicy_is_inactive(), i.e. cpumask_empty(policy->cpus), so a non-zero\nbitmap makes them run the attribute callbacks on a policy that is not\ninitialized yet.\n\nFix this by using zalloc_cpumask_var() for policy->cpus."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:22:31.046Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/0de2f3918fbbbb767e7e716178194b66560dd12a"},{"url":"https://git.kernel.org/stable/c/6e166b9281dec98aed19213a84235250e5fdb081"},{"url":"https://git.kernel.org/stable/c/bbc0472d2270bf732142ca71579d6ede636174ed"},{"url":"https://git.kernel.org/stable/c/54d37bcf2f497140b9207968557ddb484058e749"}],"title":"cpufreq: zero-initialize policy cpumask before sysfs publication","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97905","datePublished":"2026-09-25T10:22:31.046Z","dateReserved":"2026-09-25T10:18:58.200Z","dateUpdated":"2026-09-25T10:22:31.046Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:17","lastModifiedDate":"2026-09-25 11:17:17","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97905","Ordinal":"1","Title":"cpufreq: zero-initialize policy cpumask before sysfs publication","CVE":"CVE-2026-97905","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97905","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: zero-initialize policy cpumask before sysfs publication\n\ncpufreq_policy_alloc() allocates policy->cpus with alloc_cpumask_var(),\ni.e. without __GFP_ZERO, unlike the sibling related_cpus and real_cpus\nmasks. With CONFIG_CPUMASK_OFFSTACK=y the mask is a separate\nkmalloc_node() allocation, so its bitmap holds whatever the slab allocator\nleft behind:\n\n  cpufreq_online()\n    cpufreq_policy_alloc()\n      alloc_cpumask_var(&policy->cpus)    /* bitmap is uninitialized */\n      kobject_init_and_add()              /* policy%u/ appears in sysfs */\n    cpufreq_policy_online()\n      cpumask_copy(policy->cpus, cpumask_of(cpu))  /* first valid value */\n\nThis leaves a window in which the sysfs attributes are already reachable\nwhile policy->cpus is still garbage. show()/store() gate on\npolicy_is_inactive(), i.e. cpumask_empty(policy->cpus), so a non-zero\nbitmap makes them run the attribute callbacks on a policy that is not\ninitialized yet.\n\nFix this by using zalloc_cpumask_var() for policy->cpus.","Type":"Description","Title":"cpufreq: zero-initialize policy cpumask before sysfs publication"}]}}}