CVE-2024-57984: i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition
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.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel use-after-free in the DesignWare I3C master driver. A race during driver removal can leave queued work using memory that has already been freed. Impact is high because kernel memory corruption can threaten confidentiality, integrity, and availability, but exposure appears limited to affected Linux systems using this driver.
Executive priority
Treat as high priority for Linux fleets where this driver is enabled, especially embedded or hardware-adjacent systems. For general servers without I3C exposure, validate applicability before emergency action. No source provided confirms active exploitation.
Technical view
The issue is in dw_i3c_common_remove cleanup versus dw_i3c_hj_work execution. i3c_master_unregister can free master->base while queued hot-join work later calls i3c_master_do_daa using that freed object. The fix cancels the work before cleanup proceeds. CVSS 3.1 is 7.8, local, low privilege, no user interaction.
Likely exposure
Systems are likely exposed only if they run affected Linux kernel versions or downstream builds that include the dw_i3c_master DesignWare I3C driver path. The source data does not identify specific distributions, devices, or configurations beyond Linux kernel references.
Exploitation context
The bundle does not show active exploitation, and KEV is false. CVSS describes local attack conditions with low privileges and no user interaction. Public sources provided describe the race and fix, but do not provide evidence of weaponized exploitation.
Researcher notes
The core condition is a teardown race between unregister/free and queued hot-join work. The meaningful validation question is whether the affected driver code is present and reachable in the deployed kernel. The provided record does not establish distribution-specific fixed versions.
Mitigation direction
Upgrade to a kernel or vendor package containing the referenced stable fixes.
If using downstream kernels, check distribution advisories for backported fixes.
Prioritize systems with DesignWare I3C hardware or dw_i3c_master enabled.
Avoid direct wrangling of kernel modules on production systems unless operationally required.
Validation and detection
Inventory kernel versions and compare against vendor-fixed builds.
Check whether dw_i3c_master or related I3C support is present or loaded.
Review vendor kernel changelogs for CVE-2024-57984 or the referenced commits.
Confirm staging and production kernels contain the work-cancellation fix.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.