Linux: Use After Free
CVE-2025-37916 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 9b467c5bcdb45a41d2a49fbb9ffca73d1380e99b, c649b9653ed09196e91d3f4b16b679041b3c42e6, 26dc701021302f11c8350108321d11763bd81dfe 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.23% 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 9b467c5bcdb45a41d2a49fbb9ffca73d1380e99b or c649b9653ed09196e91d3f4b16b679041b3c42e6 or 26dc701021302f11c8350108321d11763bd81dfe or dfd76010f8e821b66116dec3c7d90dd2403d1396, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.90 or 6.12.28 or 6.14.6, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 10659034c622738bc1bfab8a76fc576c52d5acce up to, but not including, 9b467c5bcdb45a41d2a49fbb9ffca73d1380e99b; 10659034c622738bc1bfab8a76fc576c52d5acce up to, but not including, c649b9653ed09196e91d3f4b16b679041b3c42e6; 10659034c622738bc1bfab8a76fc576c52d5acce up to, but not including, 26dc701021302f11c8350108321d11763bd81dfe; 10659034c622738bc1bfab8a76fc576c52d5acce up to, but not including, dfd76010f8e821b66116dec3c7d90dd2403d1396; 6.4 | 9b467c5bcdb45a41d2a49fbb9ffca73d1380e99b, c649b9653ed09196e91d3f4b16b679041b3c42e6, 26dc701021302f11c8350108321d11763bd81dfe, dfd76010f8e821b66116dec3c7d90dd2403d1396 |
| Linux | Linux Kernel | 6.4 up to, but not including, 6.6.90; 6.7 up to, but not including, 6.12.28; 6.13 up to, but not including, 6.14.6; 6.15 | 6.6.90, 6.12.28, 6.14.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.
Official description
In the Linux kernel, the following vulnerability has been resolved: pds_core: remove write-after-free of client_id A use-after-free error popped up in stress testing: [Mon Apr 21 21:21:33 2025] BUG: KFENCE: use-after-free write in pdsc_auxbus_dev_del+0xef/0x160 [pds_core] [Mon Apr 21 21:21:33 2025] Use-after-free write at 0x000000007013ecd1 (in kfence-#47): [Mon Apr 21 21:21:33 2025] pdsc_auxbus_dev_del+0xef/0x160 [pds_core] [Mon Apr 21 21:21:33 2025] pdsc_remove+0xc0/0x1b0 [pds_core] [Mon Apr 21 21:21:33 2025] pci_device_remove+0x24/0x70 [Mon Apr 21 21:21:33 2025] device_release_driver_internal+0x11f/0x180 [Mon Apr 21 21:21:33 2025] driver_detach+0x45/0x80 [Mon Apr 21 21:21:33 2025] bus_remove_driver+0x83/0xe0 [Mon Apr 21 21:21:33 2025] pci_unregister_driver+0x1a/0x80 The actual device uninit usually happens on a separate thread scheduled after this code runs, but there is no guarantee of order of thread execution, so this could be a problem. There's no actual need to clear the client_id at this point, so simply remove the offending code.
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
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.