Linux Kernel up to 6.15.9/6.16.0 perf_mmap reference count

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 6.15.9/6.16.0. This affects the function perf_mmap. Performing a manipulation results in reference count. This vulnerability is known as CVE-2025-38564. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.15.9/6.16.0. This affects the function perf_mmap. The manipulation with an unknown input leads to a reference count vulnerability. CWE is classifying the issue as CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. This is going to have an impact on availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: perf/core: Handle buffer mapping fail correctly in perf_mmap() After successful allocation of a buffer or a successful attachment to an existing buffer perf_mmap() tries to map the buffer read only into the page table. If that fails, the already set up page table entries are zapped, but the other perf specific side effects of that failure are not handled. The calling code just cleans up the VMA and does not invoke perf_mmap_close(). This leaks reference counts, corrupts user->vm accounting and also results in an unbalanced invocation of event::event_mapped(). Cure this by moving the event::event_mapped() invocation before the map_range() call so that on map_range() failure perf_mmap_close() can be invoked without causing an unbalanced event::event_unmapped() call. perf_mmap_close() undoes the reference counts and eventually frees buffers.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-38564 since 04/16/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 260167 (Linux Distros Unpatched Vulnerability : CVE-2025-38564), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.15.10, 6.16.1 or 6.17-rc1 eliminates this vulnerability. Applying the patch 831e1c90a5d72e6977a57c44f47c46b73a438695/a9025f73c88d9d6e125743a43afc569da3ce5328/f74b9f4ba63ffdf597aaaa6cad7e284cb8e04820 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (260167) and CERT Bund (WID-SEC-2025-1869). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• SUSE openSUSE
• RESF Rocky Linux
• Dell Avamar
• Open Source Linux Kernel
• Dell NetWorker
• Dell Secure Connect Gateway
• IBM QRadar SIEM

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.0
• 6.1
• 6.2
• 6.3
• 6.4
• 6.5
• 6.6
• 6.7
• 6.8
• 6.9
• 6.10
• 6.11
• 6.12
• 6.13
• 6.14
• 6.15
• 6.15.0
• 6.15.1
• 6.15.2
• 6.15.3
• 6.15.4
• 6.15.5
• 6.15.6
• 6.15.7
• 6.15.8
• 6.15.9
• 6.16.0

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion