Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-53191 | First vendor Publication | 2024-12-27 |
Vendor | Cve | Last vendor Modification | 2025-01-31 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.8 | ||
Base Score | 7.8 | Environmental Score | 7.8 |
impact SubScore | 5.9 | Temporal Score | 7.8 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | High | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix warning when unbinding If there is an error during some initialization related to firmware, the buffers dp->tx_ring[i].tx_status are released. However this is released again when the device is unbinded (ath12k_pci), and we get: WARNING: CPU: 0 PID: 2098 at mm/slub.c:4689 free_large_kmalloc+0x4d/0x80 Call Trace: free_large_kmalloc ath12k_dp_free ath12k_core_deinit ath12k_pci_remove ... The issue is always reproducible from a VM because the MSI addressing initialization is failing. In order to fix the issue, just set the buffers to NULL after releasing in order to avoid the double free. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53191 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-415 | Double Free |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 02:37:54 |
|
2025-06-25 12:36:05 |
|
2025-06-24 02:42:34 |
|
2025-05-27 02:47:38 |
|
2025-03-29 03:43:49 |
|
2025-03-28 13:47:16 |
|
2025-03-28 03:21:36 |
|
2025-03-19 03:16:37 |
|
2025-03-18 03:29:36 |
|
2025-03-14 03:16:45 |
|
2025-03-06 14:13:18 |
|
2025-02-22 03:26:50 |
|
2025-01-31 21:21:01 |
|
2024-12-27 17:20:29 |
|