Linux: Use After Free
CVE-2024-58034 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 c3def10c610ae046aaa61d00528e7bd15e4ad8d3, e9d07e91de140679eeaf275f47ad154467cb9e05, c144423cb07e4e227a8572d5742ca2b36ada770d 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.24% 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 c3def10c610ae046aaa61d00528e7bd15e4ad8d3 or e9d07e91de140679eeaf275f47ad154467cb9e05 or c144423cb07e4e227a8572d5742ca2b36ada770d or 3b02273446e23961d910b50cc12528faec649fb2, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.179 or 6.1.129 or 6.6.76 or 6.12.13, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 96e5da7c842424bcf64afe1082b960b42b96190b up to, but not including, c3def10c610ae046aaa61d00528e7bd15e4ad8d3; 96e5da7c842424bcf64afe1082b960b42b96190b up to, but not including, e9d07e91de140679eeaf275f47ad154467cb9e05; 96e5da7c842424bcf64afe1082b960b42b96190b up to, but not including, c144423cb07e4e227a8572d5742ca2b36ada770d; 96e5da7c842424bcf64afe1082b960b42b96190b up to, but not including, 3b02273446e23961d910b50cc12528faec649fb2; 96e5da7c842424bcf64afe1082b960b42b96190b up to, but not including, 755e44538c190c31de9090d8e8821d228fcfd416; 96e5da7c842424bcf64afe1082b960b42b96190b up to, but not including, b9784e5cde1f9fb83661a70e580e381ae1264d12; 5.0 | c3def10c610ae046aaa61d00528e7bd15e4ad8d3, e9d07e91de140679eeaf275f47ad154467cb9e05, c144423cb07e4e227a8572d5742ca2b36ada770d, 3b02273446e23961d910b50cc12528faec649fb2, 755e44538c190c31de9090d8e8821d228fcfd416, b9784e5cde1f9fb83661a70e580e381ae1264d12 |
| Linux | Linux Kernel | 5.0 up to, but not including, 5.15.179; 5.16 up to, but not including, 6.1.129; 6.2 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 | 5.15.179, 6.1.129, 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: memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() As of_find_node_by_name() release the reference of the argument device node, tegra_emc_find_node_by_ram_code() releases some device nodes while still in use, resulting in possible UAFs. According to the bindings and the in-tree DTS files, the "emc-tables" node is always device's child node with the property "nvidia,use-ram-code", and the "lpddr2" node is a child of the "emc-tables" node. Thus utilize the for_each_child_of_node() macro and of_get_child_by_name() instead of of_find_node_by_name() to simplify the code. This bug was found by an experimental verification tool that I am developing. [krzysztof: applied v1, adjust the commit msg to incorporate v2 parts]
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
- git.kernel.org/stable/c/3b02273446e23961d910b50cc12528faec649fb2
- git.kernel.org/stable/c/755e44538c190c31de9090d8e8821d228fcfd416
- git.kernel.org/stable/c/b9784e5cde1f9fb83661a70e580e381ae1264d12
- git.kernel.org/stable/c/c144423cb07e4e227a8572d5742ca2b36ada770d
- git.kernel.org/stable/c/c3def10c610ae046aaa61d00528e7bd15e4ad8d3
- git.kernel.org/stable/c/e9d07e91de140679eeaf275f47ad154467cb9e05
Other references
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.