Microsoft · cpufreq: zero-initialize policy cpumask before sysfs publication
Affects MicrosoftSource GCVE Database
Not known to be exploited · fixed in e807920031ca32b668f9e7a1efbd21858f03d64b : update Microsoft when convenient.
Data as of 17 Nov 2026, 10:35 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- Patch
- Available – fixed in e807920031ca32b668f9e7a1efbd21858f03d64b, e13370c5b549712f49f80234df249303381c53b4, ca52482508b3ac9febe74ca4f732647d394727b8 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
This vulnerability involves the cpufreq component where the policy cpumask is not zero-initialized before sysfs publication. The information provided is minimal and does not include technical details about the impact or exploitation. The affected product is Microsoft software versions 3.0 and 4.0. No CVSS score or exploit information is available.