CVE-2025-38424
perf: Fix sample vs do_exit()
Reported by linux · Published July 25, 2025
In the Linux kernel, the following vulnerability has been resolved: perf: Fix sample vs do_exit() Baisheng Gao reported an ARM64 crash, which Mark decoded as being a synchronous external abort -- most likely due to trying to access MMIO in bad ways. The crash further shows perf trying to do a user stack sample while in exit_mmap()'s tlb_finish_mmu() -- i.e. while tearing down the address space it is trying to access. It turns out that we stop perf after we tear down the userspace mm; a receipie for disaster, since perf likes to access userspace for various reasons. Flip this order by moving up where we stop perf in do_exit(). Additionally, harden PERF_SAMPLE_CALLCHAIN and PERF_SAMPLE_STACK_USER to abort when the current task does not have an mm (exit_mm() makes sure to set current->mm = NULL; before commencing with the actual teardown). Such that CPU wide events don't trip on this same problem.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-modules-extra | Amazon Linux | 1:6.1.144-170.251.amzn2023 |
| bpftool | Amazon Linux | 6.12.35-55.103.amzn2023 |
| kernel-libbpf-static | Amazon Linux | 6.12.35-55.103.amzn2023 |
| kernel-tools | Amazon Linux | 6.12.35-55.103.amzn2023 |
| python3-perf | Amazon Linux | 1:6.1.144-170.251.amzn2023 |
| kernel-livepatch-6.1.144-170.251 | Amazon Linux | 1:1.0-0.amzn2023 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | c5ebcedb566ef17bda7b02686e0d658a7bb42ee7, c5ebcedb566ef17bda7b02686e0d658a7bb42ee7, c5ebcedb566ef17bda7b02686e0d658a7bb42ee7 |
| Linux | Linux | 3.7, 0, 5.4.295 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel-livepatch-6.1.144-170.251 | 0 |
| linux | linux_kernel | 3.7, 3.7, 3.7 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| Linux | Linux | *, 6.1.142, 6.6.95 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel-devel | 0 |
…and 3 more
Timeline
- Jul 10, 2025 CVE Published
- Jul 26, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (25 in total, the first dated here)
- Nov 17, 2025 CVE Updated
- Mar 29, 2026 Distribution Patch (243 in total, the first dated here)
- Mar 29, 2026 Security Advisory (260 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38424
vulnetix vdb fixes CVE-2025-38424
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38424/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart