CVE-2025-38563
HighIn 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 3.1 score
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected versions
Linux kernel versions
4.1
and later are affected. Fixed in
5.4.297,
5.10.241,
5.15.190,
6.1.148,
6.6.102,
6.12.42,
6.15.10,
6.16.1,
6.17
and their respective stable series.
References
The following references provide additional information about CVE-2025-38563 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
Zerodayinitiativehttps://www.zerodayinitiative.com/advisories/ZDI-25-873/Third Party Advisory
-
Mailing List Third Party Advisory
-
Mailing List Third Party Advisory
-
PatchKernel patch commithttps://git.kernel.org/stable/c/3bd518cc7ea61076bcd725e36ff0e690754977c0
-
PatchKernel patch commithttps://git.kernel.org/stable/c/65311aad4c808bedad0c05d9bb8b06c47dae73eb
-
PatchKernel patch commithttps://git.kernel.org/stable/c/6757a31a8e295ae4f01717a954afda173f25a121
Frequently asked questions
-
What is CVE-2025-38563?
CVE-2025-38563 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 4.1 onward and has been patched in 5.4.297, 5.10.241, 5.15.190 and others. CVE-2025-38563 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-38563?
CVE-2025-38563 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. -
Is there a patch available for CVE-2025-38563?
Yes — CVE-2025-38563 has been patched. Fixed versions include 5.4.297, 5.10.241, 5.15.190 and others. If you are running Linux kernel 4.1 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-38563 actively exploited?
No — CVE-2025-38563 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.