CVE-2025-38563
Description
In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have to be prevented. Implement the vm_operations_struct::may_split() callback and return unconditionally -EINVAL. That ensures that the mapping offsets and sizes cannot be changed after the fact. Remapping to a different fixed address with the same size is still possible as it takes the references for the new mapping and drops those of the old mapping.
CVSS Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Threat Intelligence
Affected Products 9
| Vendor | Product | Version | Range |
|---|---|---|---|
| linux | linux_kernel | * | ≥4.1 – <5.4.297 |
| linux | linux_kernel | * | ≥5.5 – <5.10.241 |
| linux | linux_kernel | * | ≥5.11 – <5.15.190 |
| linux | linux_kernel | * | ≥5.16 – <6.1.148 |
| linux | linux_kernel | * | ≥6.2 – <6.6.102 |
| linux | linux_kernel | * | ≥6.7 – <6.12.42 |
| linux | linux_kernel | * | ≥6.13 – <6.15.10 |
| linux | linux_kernel | * | ≥6.16 – <6.16.1 |
| debian | debian_linux | 11.0 | any |
References 12
- git.kernel.org https://git.kernel.org/stable/c/3bd518cc7ea61076bcd725e36ff0e690754977c0
- git.kernel.org https://git.kernel.org/stable/c/65311aad4c808bedad0c05d9bb8b06c47dae73eb
- git.kernel.org https://git.kernel.org/stable/c/6757a31a8e295ae4f01717a954afda173f25a121
- git.kernel.org https://git.kernel.org/stable/c/7b84cb58d1f0aa07656802eae24689566e5f5b1b
- git.kernel.org https://git.kernel.org/stable/c/b024d7b56c77191cde544f838debb7f8451cd0d6
- git.kernel.org https://git.kernel.org/stable/c/d52451a9210f2e5a079ba052918c93563518a9ff
- git.kernel.org https://git.kernel.org/stable/c/e4346ffec2c44d6b0be834d59b20632b5bb5729e
- git.kernel.org https://git.kernel.org/stable/c/e529888b7e8092912dd8789bdfc76685ccd2ff5f
- git.kernel.org https://git.kernel.org/stable/c/ff668930871e0198c7f4e325058b8b7c286787bd
- lists.debian.org https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- zerodayinitiative.com https://www.zerodayinitiative.com/advisories/ZDI-25-873/
Remediation
- git.kernel.org https://git.kernel.org/stable/c/3bd518cc7ea61076bcd725e36ff0e690754977c0
- git.kernel.org https://git.kernel.org/stable/c/65311aad4c808bedad0c05d9bb8b06c47dae73eb
- git.kernel.org https://git.kernel.org/stable/c/6757a31a8e295ae4f01717a954afda173f25a121
- git.kernel.org https://git.kernel.org/stable/c/7b84cb58d1f0aa07656802eae24689566e5f5b1b
- git.kernel.org https://git.kernel.org/stable/c/b024d7b56c77191cde544f838debb7f8451cd0d6
- git.kernel.org https://git.kernel.org/stable/c/d52451a9210f2e5a079ba052918c93563518a9ff
- git.kernel.org https://git.kernel.org/stable/c/e4346ffec2c44d6b0be834d59b20632b5bb5729e
- git.kernel.org https://git.kernel.org/stable/c/e529888b7e8092912dd8789bdfc76685ccd2ff5f
- git.kernel.org https://git.kernel.org/stable/c/ff668930871e0198c7f4e325058b8b7c286787bd