Linux: Use After Free
CVE-2025-37952 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 21100812657965dd95bc305f6076f62012f34cf4, fec1f9e9a650e8e7011330a085c77e7bf2a08ea9, 9e9841e232b51171ddf3bc4ee517d5d28dc8cad6 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.37% 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 21100812657965dd95bc305f6076f62012f34cf4 or fec1f9e9a650e8e7011330a085c77e7bf2a08ea9 or 9e9841e232b51171ddf3bc4ee517d5d28dc8cad6 or 16727e442568a46d9cca69fe2595896de86e120d, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.91 or 6.12.29 or 6.14.7, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 0626e6641f6b467447c81dd7678a69c66f7746cf up to, but not including, 21100812657965dd95bc305f6076f62012f34cf4; 0626e6641f6b467447c81dd7678a69c66f7746cf up to, but not including, fec1f9e9a650e8e7011330a085c77e7bf2a08ea9; 0626e6641f6b467447c81dd7678a69c66f7746cf up to, but not including, 9e9841e232b51171ddf3bc4ee517d5d28dc8cad6; 0626e6641f6b467447c81dd7678a69c66f7746cf up to, but not including, 16727e442568a46d9cca69fe2595896de86e120d; 0626e6641f6b467447c81dd7678a69c66f7746cf up to, but not including, 36991c1ccde2d5a521577c448ffe07fcccfe104d; 5.15 | 21100812657965dd95bc305f6076f62012f34cf4, fec1f9e9a650e8e7011330a085c77e7bf2a08ea9, 9e9841e232b51171ddf3bc4ee517d5d28dc8cad6, 16727e442568a46d9cca69fe2595896de86e120d, 36991c1ccde2d5a521577c448ffe07fcccfe104d |
| Linux | Linux Kernel | 5.15 up to, but not including, 6.6.91; 6.7 up to, but not including, 6.12.29; 6.13 up to, but not including, 6.14.7; 6.15 | 6.6.91, 6.12.29, 6.14.7 |
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.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix UAF in __close_file_table_ids A use-after-free is possible if one thread destroys the file via __ksmbd_close_fd while another thread holds a reference to it. The existing checks on fp->refcount are not sufficient to prevent this. The fix takes ft->lock around the section which removes the file from the file table. This prevents two threads acquiring the same file pointer via __close_file_table_ids, as well as the other functions which retrieve a file from the IDR and which already use this same lock.
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.
- 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.