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

TypeDescriptionCount
Application 8
Os 3700

Sources (Detail)

https://git.kernel.org/stable/c/223b546c6222d42147eff034433002ca5e2e7e09
https://git.kernel.org/stable/c/90556b96338aa6037cd26dac857327fda7c19732
https://git.kernel.org/stable/c/94c9100b600f05a36b33f9ed76dbd6fb0eb25386
https://git.kernel.org/stable/c/ca68ce0d9f4bcd032fd1334441175ae399642a06
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
9
10
11
12
13
Date Informations
2025-06-26 02:37:54
  • Multiple Updates
2025-06-25 12:36:05
  • Multiple Updates
2025-06-24 02:42:34
  • Multiple Updates
2025-05-27 02:47:38
  • Multiple Updates
2025-03-29 03:43:49
  • Multiple Updates
2025-03-28 13:47:16
  • Multiple Updates
2025-03-28 03:21:36
  • Multiple Updates
2025-03-19 03:16:37
  • Multiple Updates
2025-03-18 03:29:36
  • Multiple Updates
2025-03-14 03:16:45
  • Multiple Updates
2025-03-06 14:13:18
  • Multiple Updates
2025-02-22 03:26:50
  • Multiple Updates
2025-01-31 21:21:01
  • Multiple Updates
2024-12-27 17:20:29
  • First insertion