CVE-2025-68329
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.
Affected versions
Linux kernel versions
6.10
and later are affected. Fixed in
6.12.61,
6.17.11,
6.18
and their respective stable series.
References
The following references provide additional information about CVE-2025-68329 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/45053c12c45f0fb8ef6ab95118dd928d2fec0255
-
PatchKernel patch commithttps://git.kernel.org/stable/c/922fdd0b755a84f9933b3ca195f60092b6bb88ee
-
PatchKernel patch commithttps://git.kernel.org/stable/c/b042fdf18e89a347177a49e795d8e5184778b5b6
Frequently asked questions
-
What is CVE-2025-68329?
CVE-2025-68329 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.10 onward and has been patched in 6.12.61, 6.17.11 and 6.18. CVE-2025-68329 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2025-68329?
Yes — CVE-2025-68329 has been patched. Fixed versions include 6.12.61, 6.17.11 and 6.18. If you are running Linux kernel 6.10 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-68329 actively exploited?
No — CVE-2025-68329 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.