Linux: Use After Free
CVE-2025-38024 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 7c7c80c32e00665234e373ab03fe82f5c5c2c230, 3a3b73e135e3bd18423d0baa72571319c7feb759, f8f470e3a757425a8f98fb9a5991e3cf62fc7134 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.24% 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 7c7c80c32e00665234e373ab03fe82f5c5c2c230 or 3a3b73e135e3bd18423d0baa72571319c7feb759 or f8f470e3a757425a8f98fb9a5991e3cf62fc7134 or 52daccfc3fa68ee1902d52124921453d7a335591, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.4.294 or 5.10.238 or 5.15.184 or 6.1.140, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 7c7c80c32e00665234e373ab03fe82f5c5c2c230; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 3a3b73e135e3bd18423d0baa72571319c7feb759; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, f8f470e3a757425a8f98fb9a5991e3cf62fc7134; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 52daccfc3fa68ee1902d52124921453d7a335591; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, ee4c5a2a38596d548566560c0c022ab797e6f71a; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 336edd6b0f5b7fbffc3e065285610624f59e88df; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 16c45ced0b3839d3eee72a86bb172bef6cf58980; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, f81b33582f9339d2dc17c69b92040d3650bb4bae; and 1 more ranges | 7c7c80c32e00665234e373ab03fe82f5c5c2c230, 3a3b73e135e3bd18423d0baa72571319c7feb759, f8f470e3a757425a8f98fb9a5991e3cf62fc7134, 52daccfc3fa68ee1902d52124921453d7a335591, ee4c5a2a38596d548566560c0c022ab797e6f71a, 336edd6b0f5b7fbffc3e065285610624f59e88df |
| Linux | Linux Kernel | 4.8 up to, but not including, 5.4.294; 5.5 up to, but not including, 5.10.238; 5.11 up to, but not including, 5.15.184; 5.16 up to, but not including, 6.1.140; 6.2 up to, but not including, 6.6.92; 6.7 up to, but not including, 6.12.30; 6.13 up to, but not including, 6.14.8; 6.15 | 5.4.294, 5.10.238, 5.15.184, 6.1.140, 6.6.92, 6.12.30 |
| 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.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x7d/0xa0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcf/0x610 mm/kasan/report.c:489 kasan_report+0xb5/0xe0 mm/kasan/report.c:602 rxe_queue_cleanup+0xd0/0xe0 drivers/infiniband/sw/rxe/rxe_queue.c:195 rxe_cq_cleanup+0x3f/0x50 drivers/infiniband/sw/rxe/rxe_cq.c:132 __rxe_cleanup+0x168/0x300 drivers/infiniband/sw/rxe/rxe_pool.c:232 rxe_create_cq+0x22e/0x3a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1109 create_cq+0x658/0xb90 drivers/infiniband/core/uverbs_cmd.c:1052 ib_uverbs_create_cq+0xc7/0x120 drivers/infiniband/core/uverbs_cmd.c:1095 ib_uverbs_write+0x969/0xc90 drivers/infiniband/core/uverbs_main.c:679 vfs_write fs/read_write.c:677 [inline] vfs_write+0x26a/0xcc0 fs/read_write.c:659 ksys_write+0x1b8/0x200 fs/read_write.c:731 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f In the function rxe_create_cq, when rxe_cq_from_init fails, the function rxe_cleanup will be called to handle the allocated resources. In fact, some memory resources have already been freed in the function rxe_cq_from_init. Thus, this problem will occur. The solution is to let rxe_cleanup do all the work.
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/16c45ced0b3839d3eee72a86bb172bef6cf58980
- git.kernel.org/stable/c/336edd6b0f5b7fbffc3e065285610624f59e88df
- git.kernel.org/stable/c/3a3b73e135e3bd18423d0baa72571319c7feb759
- git.kernel.org/stable/c/52daccfc3fa68ee1902d52124921453d7a335591
- git.kernel.org/stable/c/7c7c80c32e00665234e373ab03fe82f5c5c2c230
- git.kernel.org/stable/c/ee4c5a2a38596d548566560c0c022ab797e6f71a
- git.kernel.org/stable/c/f81b33582f9339d2dc17c69b92040d3650bb4bae
- git.kernel.org/stable/c/f8f470e3a757425a8f98fb9a5991e3cf62fc7134
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2025/08/msg00010.htmlThird Party Advisory
- lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlThird Party Advisory
Recent Use After Free vulnerabilities
- 8.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.