Linux: Use After Free
CVE-2025-38259 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 edadaf4239c14dc8a19ea7f60b97d5524d93c29b, 9830ef1803a5bc50b4a984a06cf23142cd46229d, a8795f3cd289cd958f6396a1b43ba46fa8e22a2e 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.18% 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 edadaf4239c14dc8a19ea7f60b97d5524d93c29b or 9830ef1803a5bc50b4a984a06cf23142cd46229d or a8795f3cd289cd958f6396a1b43ba46fa8e22a2e or b86280aaa23c1c0f31bcaa600d35ddc45bc38b7a, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.143 or 6.6.96 or 6.12.36 or 6.15.5, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 20aedafdf4926e7a957f8b302a18c8fb75c7e332 up to, but not including, edadaf4239c14dc8a19ea7f60b97d5524d93c29b; 20aedafdf4926e7a957f8b302a18c8fb75c7e332 up to, but not including, 9830ef1803a5bc50b4a984a06cf23142cd46229d; 20aedafdf4926e7a957f8b302a18c8fb75c7e332 up to, but not including, a8795f3cd289cd958f6396a1b43ba46fa8e22a2e; 20aedafdf4926e7a957f8b302a18c8fb75c7e332 up to, but not including, b86280aaa23c1c0f31bcaa600d35ddc45bc38b7a; 20aedafdf4926e7a957f8b302a18c8fb75c7e332 up to, but not including, 9079db287fc3e38e040b0edeb0a25770bb679c8e; 5.1 | edadaf4239c14dc8a19ea7f60b97d5524d93c29b, 9830ef1803a5bc50b4a984a06cf23142cd46229d, a8795f3cd289cd958f6396a1b43ba46fa8e22a2e, b86280aaa23c1c0f31bcaa600d35ddc45bc38b7a, 9079db287fc3e38e040b0edeb0a25770bb679c8e |
| Linux | Linux Kernel | 5.1 up to, but not including, 6.1.143; 6.2 up to, but not including, 6.6.96; 6.7 up to, but not including, 6.12.36; 6.13 up to, but not including, 6.15.5 | 6.1.143, 6.6.96, 6.12.36, 6.15.5 |
| Debian | Debian Linux | 11.0 | Not stated |
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: ASoC: codecs: wcd9335: Fix missing free of regulator supplies Driver gets and enables all regulator supplies in probe path (wcd9335_parse_dt() and wcd9335_power_on_reset()), but does not cleanup in final error paths and in unbind (missing remove() callback). This leads to leaked memory and unbalanced regulator enable count during probe errors or unbind. Fix this by converting entire code into devm_regulator_bulk_get_enable() which also greatly simplifies the 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
- git.kernel.org/stable/c/9079db287fc3e38e040b0edeb0a25770bb679c8e
- git.kernel.org/stable/c/9830ef1803a5bc50b4a984a06cf23142cd46229d
- git.kernel.org/stable/c/a8795f3cd289cd958f6396a1b43ba46fa8e22a2e
- git.kernel.org/stable/c/b86280aaa23c1c0f31bcaa600d35ddc45bc38b7a
- git.kernel.org/stable/c/edadaf4239c14dc8a19ea7f60b97d5524d93c29b
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlMailing List, Third Party Advisory
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.