Linux: Use After Free
CVE-2024-57984 is a high-severity use after free vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 60d2fb033a999bb644f8e8606ff4a1b82de36c6f, 9b0063098fcde17cd2894f2c96459b23388507ca, fc84dd3c909a372c0d130f5f84c404717c17eed8 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.23% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 60d2fb033a999bb644f8e8606ff4a1b82de36c6f or 9b0063098fcde17cd2894f2c96459b23388507ca or fc84dd3c909a372c0d130f5f84c404717c17eed8 or b75439c945b94dd8a2b645355bdb56f948052601, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.76 or 6.12.13 or 6.13.2, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef up to, but not including, 60d2fb033a999bb644f8e8606ff4a1b82de36c6f; 1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef up to, but not including, 9b0063098fcde17cd2894f2c96459b23388507ca; 1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef up to, but not including, fc84dd3c909a372c0d130f5f84c404717c17eed8; 1dd728f5d4d4b8b53196c1e0fcf86bbaaee39cef up to, but not including, b75439c945b94dd8a2b645355bdb56f948052601; 5.0 | 60d2fb033a999bb644f8e8606ff4a1b82de36c6f, 9b0063098fcde17cd2894f2c96459b23388507ca, fc84dd3c909a372c0d130f5f84c404717c17eed8, b75439c945b94dd8a2b645355bdb56f948052601 |
| Linux | Linux Kernel | 5.0 up to, but not including, 6.6.76; 6.7 up to, but not including, 6.12.13; 6.13 up to, but not including, 6.13.2 | 6.6.76, 6.12.13, 6.13.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
Spotted an error? Tell us.