CVE-2026-97905: cpufreq: zero-initialize policy cpumask before sysfs publication
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 06f273d29e5e0fe5c775a65c563fbeed8cd94c7a, 0de2f3918fbbbb767e7e716178194b66560dd12a, 54d37bcf2f497140b9207968557ddb484058e749; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 06f273d29e5e0fe5c775a65c563fbeed8cd94c7a, 0de2f3918fbbbb767e7e716178194b66560dd12a, 54d37bcf2f497140b9207968557ddb484058e749; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.2affected
- 2fc3384dc75bf7333384c7a16d12c796f61c3f56 and later · before e13370c5b549712f49f80234df249303381c53b4affected · git
- 2fc3384dc75bf7333384c7a16d12c796f61c3f56 and later · before e807920031ca32b668f9e7a1efbd21858f03d64baffected · git
- 2fc3384dc75bf7333384c7a16d12c796f61c3f56 and later · before ca52482508b3ac9febe74ca4f732647d394727b8affected · git
- 2fc3384dc75bf7333384c7a16d12c796f61c3f56 and later · before 06f273d29e5e0fe5c775a65c563fbeed8cd94c7aaffected · git
- 2fc3384dc75bf7333384c7a16d12c796f61c3f56 and later · before 0de2f3918fbbbb767e7e716178194b66560dd12aaffected · git
- 2fc3384dc75bf7333384c7a16d12c796f61c3f56 and later · before 6e166b9281dec98aed19213a84235250e5fdb081affected · git
- 2fc3384dc75bf7333384c7a16d12c796f61c3f56 and later · before bbc0472d2270bf732142ca71579d6ede636174edaffected · git
- 2fc3384dc75bf7333384c7a16d12c796f61c3f56 and later · before 54d37bcf2f497140b9207968557ddb484058e749affected · git
- before 4.2not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97903Sep 25, 2026 · exit: hold a reference to thread_pid across proc_flush_pid31Monitor
- ← EarlierCVE-2026-97904Sep 25, 2026 · cpufreq: initialize policy rwsem before sysfs publication0Monitor
- Later →CVE-2026-97906Sep 25, 2026 · bootconfig: Fix integer overflow in initrd size check0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 06f273d29e5e0fe5c775a65c563fbeed8cd94c7a | Vendor (CNA) |
| Linux Linux | 0de2f3918fbbbb767e7e716178194b66560dd12a | Vendor (CNA) |
| Linux Linux | 54d37bcf2f497140b9207968557ddb484058e749 | Vendor (CNA) |
| Linux Linux | 6e166b9281dec98aed19213a84235250e5fdb081 | Vendor (CNA) |
| Linux Linux | bbc0472d2270bf732142ca71579d6ede636174ed | Vendor (CNA) |
| Linux Linux | ca52482508b3ac9febe74ca4f732647d394727b8 | Vendor (CNA) |
| Linux Linux | e13370c5b549712f49f80234df249303381c53b4 | Vendor (CNA) |
| Linux Linux | e807920031ca32b668f9e7a1efbd21858f03d64b | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/0de2f3918fbbbb767e7e716178194b66560dd12a
- git.kernel.org/stable/c/54d37bcf2f497140b9207968557ddb484058e749
- git.kernel.org/stable/c/6e166b9281dec98aed19213a84235250e5fdb081
- git.kernel.org/stable/c/bbc0472d2270bf732142ca71579d6ede636174ed
- git.kernel.org/stable/c/ca52482508b3ac9febe74ca4f732647d394727b8
- git.kernel.org/stable/c/e13370c5b549712f49f80234df249303381c53b4
- git.kernel.org/stable/c/e807920031ca32b668f9e7a1efbd21858f03d64b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.