Linux: Use After Free
CVE-2024-47750 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 2ccf1c75d39949d8ea043d04a2e92d7100ea723d, d2d9c5127122745da6e887f451dd248cfeffca33, dac2723d8bfa9cf5333f477741e6e5fa1ed34645 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.21% 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 2ccf1c75d39949d8ea043d04a2e92d7100ea723d or d2d9c5127122745da6e887f451dd248cfeffca33 or dac2723d8bfa9cf5333f477741e6e5fa1ed34645 or 60595923371c2ebe7faf82536c47eb0c967e3425, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.113 or 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 | 70f92521584f1d1e8268311ee84413307b0fdea8 up to, but not including, 2ccf1c75d39949d8ea043d04a2e92d7100ea723d; 70f92521584f1d1e8268311ee84413307b0fdea8 up to, but not including, d2d9c5127122745da6e887f451dd248cfeffca33; 70f92521584f1d1e8268311ee84413307b0fdea8 up to, but not including, dac2723d8bfa9cf5333f477741e6e5fa1ed34645; 70f92521584f1d1e8268311ee84413307b0fdea8 up to, but not including, 60595923371c2ebe7faf82536c47eb0c967e3425; 70f92521584f1d1e8268311ee84413307b0fdea8 up to, but not including, fd8489294dd2beefb70f12ec4f6132aeec61a4d0; 5.18 | 2ccf1c75d39949d8ea043d04a2e92d7100ea723d, d2d9c5127122745da6e887f451dd248cfeffca33, dac2723d8bfa9cf5333f477741e6e5fa1ed34645, 60595923371c2ebe7faf82536c47eb0c967e3425, fd8489294dd2beefb70f12ec4f6132aeec61a4d0 |
| Linux | Linux Kernel | 5.18 up to, but not including, 6.1.113; 6.2 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.1.113, 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: RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 Currently rsv_qp is freed before ib_unregister_device() is called on HIP08. During the time interval, users can still dereg MR and rsv_qp will be used in this process, leading to a UAF. Move the release of rsv_qp after calling ib_unregister_device() to fix it.
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
- git.kernel.org/stable/c/2ccf1c75d39949d8ea043d04a2e92d7100ea723d
- git.kernel.org/stable/c/60595923371c2ebe7faf82536c47eb0c967e3425
- git.kernel.org/stable/c/d2d9c5127122745da6e887f451dd248cfeffca33
- git.kernel.org/stable/c/dac2723d8bfa9cf5333f477741e6e5fa1ed34645
- git.kernel.org/stable/c/fd8489294dd2beefb70f12ec4f6132aeec61a4d0
Other references
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.