CVE-2025-38563: Linux Kernel perf Subsystem AUX Buffers Use-After-Free Local Privilege Escalation Vulnerability

Published Aug 19, 2025
·
Updated

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 perfmmapopen() calls, which take reference counts, but then the subsequent perfmmapclose() 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 vmoperationsstruct::maysplit() 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.

Other sources

This vulnerability allows local attackers to escalate privileges on affected installations of Linux Kernel. An attacker must first obtain the ability to execute high-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the handling of reference counters. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the kernel.

ZDI

Affected Software

14 affected componentsFixes available
Linux Linux kernel
Linux Kernel
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
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.96.2-1

Event History

Aug 19, 2025
CVE Published
via MITRE·05:02 PM
Data Sourced
via MITRE·05:02 PM
Description
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·03:47 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·10:47 AM
DescriptionSeverity
Updated
via Microsoft·10:47 AM
SeverityAffected Software
Oct 10, 2025
Advisory Published
via ZDI·03:43 PM
Data Sourced
via ZDI·03:43 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-38563?

CVE-2025-38563 is classified as a medium severity vulnerability in the Linux kernel.

2

How do I fix CVE-2025-38563?

To fix CVE-2025-38563, update your Linux kernel to the latest patched version provided by your distribution.

3

What impact does CVE-2025-38563 have on system security?

CVE-2025-38563 could potentially allow unauthorized access or manipulation of memory mappings affecting system stability.

4

Which versions of the Linux kernel are affected by CVE-2025-38563?

CVE-2025-38563 affects multiple versions of the Linux kernel prior to the latest security patches.

5

Is CVE-2025-38563 remotely exploitable?

CVE-2025-38563 is not remotely exploitable, as it requires local access to the system to be an effective threat.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203