Linux: Use After Free
CVE-2024-47675 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 790c630ab0e7d7aba6d186581d4627c09fce60f3, 7c1d782e5afbf7c50ba74ecc4ddc18a05d63e5ee, cdf27834c3dd5d9abf7eb8e4ee87ee9e307eb25c 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 790c630ab0e7d7aba6d186581d4627c09fce60f3 or 7c1d782e5afbf7c50ba74ecc4ddc18a05d63e5ee or cdf27834c3dd5d9abf7eb8e4ee87ee9e307eb25c or 5fe6e308abaea082c20fbf2aa5df8e14495622cf, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.54 or 6.10.13 or 6.11.2, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 89ae89f53d201143560f1e9ed4bfa62eee34f88e up to, but not including, 790c630ab0e7d7aba6d186581d4627c09fce60f3; 89ae89f53d201143560f1e9ed4bfa62eee34f88e up to, but not including, 7c1d782e5afbf7c50ba74ecc4ddc18a05d63e5ee; 89ae89f53d201143560f1e9ed4bfa62eee34f88e up to, but not including, cdf27834c3dd5d9abf7eb8e4ee87ee9e307eb25c; 89ae89f53d201143560f1e9ed4bfa62eee34f88e up to, but not including, 5fe6e308abaea082c20fbf2aa5df8e14495622cf; 6.6 | 790c630ab0e7d7aba6d186581d4627c09fce60f3, 7c1d782e5afbf7c50ba74ecc4ddc18a05d63e5ee, cdf27834c3dd5d9abf7eb8e4ee87ee9e307eb25c, 5fe6e308abaea082c20fbf2aa5df8e14495622cf |
| Linux | Linux Kernel | 6.6 up to, but not including, 6.6.54; 6.7 up to, but not including, 6.10.13; 6.11 up to, but not including, 6.11.2 | 6.6.54, 6.10.13, 6.11.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 NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix use-after-free in bpf_uprobe_multi_link_attach() If bpf_link_prime() fails, bpf_uprobe_multi_link_attach() goes to the error_free label and frees the array of bpf_uprobe's without calling bpf_uprobe_unregister(). This leaks bpf_uprobe->uprobe and worse, this frees bpf_uprobe->consumer without removing it from the uprobe->consumers list.
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: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Use After Free vulnerabilities
- 7.0 High severity
- 7.0 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.