Answer in brief
CVE-2024-49874 records a High severity (CVSS 7.8) vulnerability in i3c: master: svc: Fix use after free vulnerability in svc_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.
CVSS is 7.8. 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 | >=87e0f28eda36c7843523aa8dd0c5dab3331e9718 <56bddf543d4d7ddeff3f87b554ddacfdf086bffe || >=0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7 <4ac637122930cc4ab7e2c22e364cf3aaf96b05b1 || >=0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7 <4318998892bf8fe99f97bea18c37ae7b685af75a || >=0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7 <27b55724d3f781dd6e635e89dc6e2fd78fa81a00 || >=0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7 <61850725779709369c7e907ae8c7c75dc7cec4f3 | 56bddf543d4d7ddeff3f87b554ddacfdf086bffe, 4ac637122930cc4ab7e2c22e364cf3aaf96b05b1, 4318998892bf8fe99f97bea18c37ae7b685af75a, 27b55724d3f781dd6e635e89dc6e2fd78fa81a00, 61850725779709369c7e907ae8c7c75dc7cec4f3 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Oct 21, 2024
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: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition In the svc_i3c_master_probe function, &master->hj_work is bound with svc_i3c_master_hj_work, &master->ibi_work is bound with svc_i3c_master_ibi_work. And svc_i3c_master_ibi_work can start the hj_work, svc_i3c_master_irq_handler can start the ibi_work. If we remove the module which will call svc_i3c_master_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 | svc_i3c_master_hj_work svc_i3c_master_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 svc_i3c_master_remove.
Quoted source text, attributed separately from HOL analysis.