Linux: Use After Free
CVE-2024-26592 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 999daf367b924fdf14e9d83e034ee0f86bc17ec6, 380965e48e9c32ee4263c023e1d830ea7e462ed1, 24290ba94cd0136e417283b0dbf8fcdabcf62111 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.97% chance of exploitation within 30 days, higher than 63% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 999daf367b924fdf14e9d83e034ee0f86bc17ec6 or 380965e48e9c32ee4263c023e1d830ea7e462ed1 or 24290ba94cd0136e417283b0dbf8fcdabcf62111 or 69d54650b751532d1e1613a4fb433e591aeef126, whichever matches your release line, or a later version.
- Update linux_kernel to 999daf367b92 or 380965e48e9c or 24290ba94cd0 or 69d54650b751, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | a848c4f15ab6d5d405dbee7de5da71839b2bf35e up to, but not including, 999daf367b924fdf14e9d83e034ee0f86bc17ec6; a848c4f15ab6d5d405dbee7de5da71839b2bf35e up to, but not including, 380965e48e9c32ee4263c023e1d830ea7e462ed1; a848c4f15ab6d5d405dbee7de5da71839b2bf35e up to, but not including, 24290ba94cd0136e417283b0dbf8fcdabcf62111; a848c4f15ab6d5d405dbee7de5da71839b2bf35e up to, but not including, 69d54650b751532d1e1613a4fb433e591aeef126; a848c4f15ab6d5d405dbee7de5da71839b2bf35e up to, but not including, 38d20c62903d669693a1869aa68c4dd5674e2544; 5.15 | 999daf367b924fdf14e9d83e034ee0f86bc17ec6, 380965e48e9c32ee4263c023e1d830ea7e462ed1, 24290ba94cd0136e417283b0dbf8fcdabcf62111, 69d54650b751532d1e1613a4fb433e591aeef126, 38d20c62903d669693a1869aa68c4dd5674e2544 |
| Linux | linux_kernel | 5.15; a848c4f15ab6 up to, but not including, 999daf367b92; a848c4f15ab6 up to, but not including, 380965e48e9c; a848c4f15ab6 up to, but not including, 24290ba94cd0; a848c4f15ab6 up to, but not including, 69d54650b751; a848c4f15ab6 up to, but not including, 38d20c62903d | 999daf367b92, 380965e48e9c, 24290ba94cd0, 69d54650b751, 38d20c62903d |
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 | 9.8 | Critical | 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: ksmbd: fix UAF issue in ksmbd_tcp_new_connection() The race is between the handling of a new TCP connection and its disconnection. It leads to UAF on `struct tcp_transport` in ksmbd_tcp_new_connection() function.
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/24290ba94cd0136e417283b0dbf8fcdabcf62111
- git.kernel.org/stable/c/380965e48e9c32ee4263c023e1d830ea7e462ed1
- git.kernel.org/stable/c/38d20c62903d669693a1869aa68c4dd5674e2544
- git.kernel.org/stable/c/69d54650b751532d1e1613a4fb433e591aeef126
- git.kernel.org/stable/c/999daf367b924fdf14e9d83e034ee0f86bc17ec6
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
- 8.8 High severity
Spotted an error? Tell us.