tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 45053c12c45f0fb8ef6ab95118dd928d2fec0255, Kernel 922fdd0b755a84f9933b3ca195f60092b6bb88ee and Kernel b042fdf18e89a347177a49e795d8e5184778b5b6.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.10, >=cf9f0f7c4c5bb45e7bb270e48bab6f7837825a64 <45053c12c45f0fb8ef6ab95118dd928d2fec0255, >=cf9f0f7c4c5bb45e7bb270e48bab6f7837825a64 <922fdd0b755a84f9933b3ca195f60092b6bb88ee, >=cf9f0f7c4c5bb45e7bb270e48bab6f7837825a64 <b042fdf18e89a347177a49e795d8e5184778b5b6 | 45053c12c45f0fb8ef6ab95118dd928d2fec0255, 922fdd0b755a84f9933b3ca195f60092b6bb88ee, b042fdf18e89a347177a49e795d8e5184778b5b6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket