Executive Summary

Informations
Name CVE-2024-57984 First vendor Publication 2025-02-27
Vendor Cve Last vendor Modification 2025-03-24

Security-Database Scoring CVSS v3

Cvss vector : N/A
Overall CVSS Score NA
Base Score NA Environmental Score NA
impact SubScore NA Temporal Score NA
Exploitabality Sub Score NA
 
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:

i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition

In dw_i3c_common_probe, &master->hj_work is bound with dw_i3c_hj_work. And dw_i3c_master_irq_handler can call dw_i3c_master_irq_handle_ibis function to start the work.

If we remove the module which will call dw_i3c_common_remove to make cleanup, it will free master->base through i3c_master_unregister while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows:

CPU0 CPU1

| dw_i3c_hj_work dw_i3c_common_remove | i3c_master_unregister(&master->base) | device_unregister(&master->dev) | device_release | //free master->base |
| i3c_master_do_daa(&master->base)
| //use master->base

Fix it by ensuring that the work is canceled before proceeding with the cleanup in dw_i3c_common_remove.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57984

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 8
Os 3701

Sources (Detail)

https://git.kernel.org/stable/c/60d2fb033a999bb644f8e8606ff4a1b82de36c6f
https://git.kernel.org/stable/c/9b0063098fcde17cd2894f2c96459b23388507ca
https://git.kernel.org/stable/c/b75439c945b94dd8a2b645355bdb56f948052601
https://git.kernel.org/stable/c/fc84dd3c909a372c0d130f5f84c404717c17eed8
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
Date Informations
2025-03-28 17:20:55
  • Multiple Updates
2025-03-28 13:48:08
  • Multiple Updates
2025-03-28 03:22:44
  • Multiple Updates
2025-03-25 03:30:36
  • Multiple Updates
2025-03-25 00:20:55
  • Multiple Updates
2025-02-28 03:46:08
  • Multiple Updates
2025-02-28 03:45:07
  • Multiple Updates
2025-02-27 21:20:33
  • Multiple Updates
2025-02-27 09:20:32
  • First insertion