CVE-2021-47313: cpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init
It's a classic example of memleak, we allocate something, we fail and
never free the resources.
Make sure we free all resources on policy ->init() failures.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-leak flaw in the CPPC CPU frequency driver. If initialization fails, allocated resources may not be freed. The business risk is reliability and resource-exhaustion impact on affected Linux systems, especially where the relevant cpufreq/CPPC path is used.
Executive priority
Treat as a high-priority Linux kernel maintenance item, not an emergency internet-facing incident based on current evidence. Prioritize patching production Linux systems where kernel reliability matters, especially fleets using CPU frequency management.
Technical view
CVE-2021-47313 resolves a resource leak in `cppc_cpufreq_cpu_init`: memory allocated during policy initialization was not released on failure paths. The source classifies it as CWE-400 with CVSS 8.4 and local attack vector. Kernel stable commits are cited as fixes, but distro-specific applicability must be verified.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds with the CPPC cpufreq code path present or enabled. The bundle lists Linux kernel version entries including 5.11, 5.12.19, 5.13.4, and 5.14, but exact downstream package status requires vendor confirmation.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. The CVSS vector is local, low complexity, no privileges, and no user interaction. Available evidence supports a kernel resource-management issue, not remote exploitation.
Researcher notes
Analysis is constrained to the supplied CVE bundle. The root issue is a failure-path cleanup bug in CPPC cpufreq initialization. The bundle provides fix commits but not exploit details, operational prerequisites, or distro package mappings.
Mitigation direction
Update affected Linux kernels using vendor or distribution guidance.
Confirm the fix includes the referenced upstream stable commits.
Reboot systems after kernel updates so the patched kernel is active.
Prioritize Linux hosts using CPPC/cpufreq functionality.
Track vendor advisories for backported fixes and exact package versions.
Validation and detection
Inventory Linux kernel versions across affected fleets.
Check whether CPPC cpufreq support is present or enabled.
Verify running kernels include the referenced stable fixes.
Review vendor advisories for distribution-specific affected packages.
Monitor affected systems for abnormal memory pressure or instability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.