Answer in brief
CVE-2024-57984 records a Unknown severity vulnerability in i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef <60d2fb033a999bb644f8e8606ff4a1b82de36c6f || >=1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef <9b0063098fcde17cd2894f2c96459b23388507ca || >=1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef <fc84dd3c909a372c0d130f5f84c404717c17eed8 || >=1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef <b75439c945b94dd8a2b645355bdb56f948052601 | 60d2fb033a999bb644f8e8606ff4a1b82de36c6f, 9b0063098fcde17cd2894f2c96459b23388507ca, fc84dd3c909a372c0d130f5f84c404717c17eed8, b75439c945b94dd8a2b645355bdb56f948052601 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-57984 records a Unknown severity vulnerability in i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef <60d2fb033a999bb644f8e8606ff4a1b82de36c6f || >=1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef <9b0063098fcde17cd2894f2c96459b23388507ca || >=1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef <fc84dd3c909a372c0d130f5f84c404717c17eed8 || >=1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef <b75439c945b94dd8a2b645355bdb56f948052601 | 60d2fb033a999bb644f8e8606ff4a1b82de36c6f, 9b0063098fcde17cd2894f2c96459b23388507ca, fc84dd3c909a372c0d130f5f84c404717c17eed8, b75439c945b94dd8a2b645355bdb56f948052601 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.