CVE-2025-68329
tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs
Reported by linux · Published December 22, 2025
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs When a VMA is split (e.g., by partial munmap or MAP_FIXED), the kernel calls vm_ops->close on each portion. For trace buffer mappings, this results in ring_buffer_unmap() being called multiple times while ring_buffer_map() was only called once. This causes ring_buffer_unmap() to return -ENODEV on subsequent calls because user_mapped is already 0, triggering a WARN_ON. Trace buffer mappings cannot support partial mappings because the ring buffer structure requires the complete buffer including the meta page. Fix this by adding a may_split callback that returns -EINVAL to prevent VMA splits entirely.
EPSS 0.18% · 8.0th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| python3-perf6.12 | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-libbpf-devel | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-modules-extra | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel6.12 | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.63-84.121.amzn2023 |
| linux_kernel | linux | 6.18, 6.17.11, 6.12.61 |
| Linux | Linux | b042fdf18e89a347177a49e795d8e5184778b5b6, 922fdd0b755a84f9933b3ca195f60092b6bb88ee, 45053c12c45f0fb8ef6ab95118dd928d2fec0255 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | cf9f0f7c4c5bb45e7bb270e48bab6f7837825a64, cf9f0f7c4c5bb45e7bb270e48bab6f7837825a64, cf9f0f7c4c5bb45e7bb270e48bab6f7837825a64 |
| Linux | Linux | 6.10, 0, 6.12.61 |
| linux | linux_kernel | 6.10, 6.10, 6.10 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| Linux | Linux | 6.12.61, 6.18, 6.17.11 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel-livepatch-6.12.63-84.121 | 0 |
| amazon:2023 | kernel6.12-libbpf | 0 |
| amazon:2023 | bpftool6.12 | 0 |
Timeline
- Dec 22, 2025 CVE Published
- Dec 23, 2025 EPSS Score (30 in total, the first dated here)
- Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (68 in total, the first dated here)
- Mar 29, 2026 Security Advisory (72 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-68329
vulnetix vdb fixes CVE-2025-68329
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-68329/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart