Linux Kernel up to 5.12.18/5.13.3 cpufreq cppc_cpufreq_cpu_init memory leak

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.12.18/5.13.3. This issue affects the function cppc_cpufreq_cpu_init of the component cpufreq. Executing a manipulation can lead to memory leak.
This vulnerability is handled as CVE-2021-47313. There is not any exploit available.
You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Linux Kernel up to 5.12.18/5.13.3. This vulnerability affects the function cppc_cpufreq_cpu_init of the component cpufreq. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. CVE summarizes:
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.
The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2021-47313 since 05/21/2024. The exploitation appears to be difficult. There are known technical details, but no exploit is available.
Upgrading to version 5.12.19 or 5.13.4 eliminates this vulnerability. Applying the patch b77538335575/e1b2b2b61d30/fe2535a44904 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 5.12.0
- 5.12.1
- 5.12.2
- 5.12.3
- 5.12.4
- 5.12.5
- 5.12.6
- 5.12.7
- 5.12.8
- 5.12.9
- 5.12.10
- 5.12.11
- 5.12.12
- 5.12.13
- 5.12.14
- 5.12.15
- 5.12.16
- 5.12.17
- 5.12.18
- 5.13.0
- 5.13.1
- 5.13.2
- 5.13.3
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory leakCWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 5.12.19/5.13.4
Patch: b77538335575/e1b2b2b61d30/fe2535a44904
Timeline
05/21/2024 🔍05/21/2024 🔍
05/21/2024 🔍
05/21/2024 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2021-47313 (🔍)
GCVE (CVE): GCVE-0-2021-47313
GCVE (VulDB): GCVE-100-265456
Entry
Created: 05/21/2024 17:57Changes: 05/21/2024 17:57 (58)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.