Linux Kernel up to 6.12.7 current_limit_map_size allocation of resources

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 5.10.232/5.15.175/6.1.122/6.6.68/6.12.7. It has been rated as problematic. The impacted element is the function current_limit_map_size. The manipulation leads to allocation of resources.
This vulnerability is documented as CVE-2024-57792. There is not any exploit available.
Upgrading the affected component is advised.
Details
A vulnerability was found in Linux Kernel up to 5.10.232/5.15.175/6.1.122/6.6.68/6.12.7. It has been rated as problematic. This issue affects the function current_limit_map_size. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. The impact remains unknown. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: power: supply: gpio-charger: Fix set charge current limits Fix set charge current limits for devices which allow to set the lowest charge current limit to be greater zero. If requested charge current limit is below lowest limit, the index equals current_limit_map_size which leads to accessing memory beyond allocated memory.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2024-57792 since 01/11/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 216460 (SUSE SLES15 Security Update : kernel (SUSE-SU-2025:0577-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.10.233, 5.15.176, 6.1.123, 6.6.69 or 6.12.8 eliminates this vulnerability. Applying the patch b29c7783ac1fe36d639c089cf471ac7a46df05f0/c3703d9340ca2820e1ac63256f4b423ea8559831/6abbbd8286b6f944eecf3c74444c138590135211/13eb3cae1d8e23cce96c095abe34da8028c09ac5/f6279a98db132da0cfff18712a1b06478c32007f/afc6e39e824ad0e44b2af50a97885caec8d213d1 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.
The vulnerability is also documented in the databases at Tenable (216460) and CERT Bund (WID-SEC-2025-0047). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- RESF Rocky Linux
- Dell NetWorker
- Dell Avamar
- Red Hat OpenShift
- IBM QRadar SIEM
- Dell PowerProtect Data Domain
- Open Source Linux Kernel
- Dell Secure Connect Gateway
Product
Type
Vendor
Name
Version
- 5.10.232
- 5.15.175
- 6.1.122
- 6.6.0
- 6.6.1
- 6.6.2
- 6.6.3
- 6.6.4
- 6.6.5
- 6.6.6
- 6.6.7
- 6.6.8
- 6.6.9
- 6.6.10
- 6.6.11
- 6.6.12
- 6.6.13
- 6.6.14
- 6.6.15
- 6.6.16
- 6.6.17
- 6.6.18
- 6.6.19
- 6.6.20
- 6.6.21
- 6.6.22
- 6.6.23
- 6.6.24
- 6.6.25
- 6.6.26
- 6.6.27
- 6.6.28
- 6.6.29
- 6.6.30
- 6.6.31
- 6.6.32
- 6.6.33
- 6.6.34
- 6.6.35
- 6.6.36
- 6.6.37
- 6.6.38
- 6.6.39
- 6.6.40
- 6.6.41
- 6.6.42
- 6.6.43
- 6.6.44
- 6.6.45
- 6.6.46
- 6.6.47
- 6.6.48
- 6.6.49
- 6.6.50
- 6.6.51
- 6.6.52
- 6.6.53
- 6.6.54
- 6.6.55
- 6.6.56
- 6.6.57
- 6.6.58
- 6.6.59
- 6.6.60
- 6.6.61
- 6.6.62
- 6.6.63
- 6.6.64
- 6.6.65
- 6.6.66
- 6.6.67
- 6.6.68
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
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: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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 |
Nessus ID: 216460
Nessus Name: SUSE SLES15 Security Update : kernel (SUSE-SU-2025:0577-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 5.10.233/5.15.176/6.1.123/6.6.69/6.12.8
Patch: b29c7783ac1fe36d639c089cf471ac7a46df05f0/c3703d9340ca2820e1ac63256f4b423ea8559831/6abbbd8286b6f944eecf3c74444c138590135211/13eb3cae1d8e23cce96c095abe34da8028c09ac5/f6279a98db132da0cfff18712a1b06478c32007f/afc6e39e824ad0e44b2af50a97885caec8d213d1
Timeline
01/11/2025 🔍01/11/2025 🔍
01/11/2025 🔍
01/25/2026 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2024-57792 (🔍)
GCVE (CVE): GCVE-0-2024-57792
GCVE (VulDB): GCVE-100-291221
CERT Bund: WID-SEC-2025-0047 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 01/11/2025 16:18Updated: 01/25/2026 20:27
Changes: 01/11/2025 16:18 (57), 02/19/2025 12:25 (2), 10/16/2025 19:58 (12), 01/25/2026 20:27 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.