Linux: Use After Free
CVE-2024-50125 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 678386459ffc07d2fbfbfe33456013786975cfef, 74a466a15731a754bcd8b5a83c126b5122e15a45, 9ddda5d967e84796e7df1b54a55f36b4b9f21079 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.34% 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 678386459ffc07d2fbfbfe33456013786975cfef or 74a466a15731a754bcd8b5a83c126b5122e15a45 or 9ddda5d967e84796e7df1b54a55f36b4b9f21079 or d30803f6a972b5b9e26d1d43b583c7ec151de04b, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.115 or 6.6.59 or 6.11.6, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | a1073aad497d0d071a71f61b721966a176d50c08 up to, but not including, 678386459ffc07d2fbfbfe33456013786975cfef; ba316be1b6a00db7126ed9a39f9bee434a508043 up to, but not including, 74a466a15731a754bcd8b5a83c126b5122e15a45; ba316be1b6a00db7126ed9a39f9bee434a508043 up to, but not including, 9ddda5d967e84796e7df1b54a55f36b4b9f21079; ba316be1b6a00db7126ed9a39f9bee434a508043 up to, but not including, d30803f6a972b5b9e26d1d43b583c7ec151de04b; ba316be1b6a00db7126ed9a39f9bee434a508043 up to, but not including, 80b05fbfa998480fb3d5299d93eab946f51e9c36; ba316be1b6a00db7126ed9a39f9bee434a508043 up to, but not including, 1bf4470a3939c678fb822073e9ea77a0560bc6bb; fea63ccd928c01573306983346588b26cffb5572; 48669c81a65628ef234cbdd91b9395952c7c27fe; and 10 more ranges | 678386459ffc07d2fbfbfe33456013786975cfef, 74a466a15731a754bcd8b5a83c126b5122e15a45, 9ddda5d967e84796e7df1b54a55f36b4b9f21079, d30803f6a972b5b9e26d1d43b583c7ec151de04b, 80b05fbfa998480fb3d5299d93eab946f51e9c36, 1bf4470a3939c678fb822073e9ea77a0560bc6bb |
| Linux | Linux Kernel | 5.15 up to, but not including, 6.1.115; 6.2 up to, but not including, 6.6.59; 6.7 up to, but not including, 6.11.6; 4.14.263; 4.19.207; 5.4.148; 5.10.67; 5.13.19; and 2 more ranges | 6.1.115, 6.6.59, 6.11.6 |
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 | 8.0 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix UAF on sco_sock_timeout conn->sk maybe have been unlinked/freed while waiting for sco_conn_lock so this checks if the conn->sk is still valid by checking if it part of sco_sk_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: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.