CVE-2025-38564
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-08-19

Last updated on: 2025-11-28

Assigner: kernel.org

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-08-19
Last Modified
2025-11-28
Generated
2026-05-06
AI Q&A
2025-08-19
EPSS Evaluated
2026-05-05
NVD
CVE-2025-38564
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.14 (inc) to 6.15.10 (exc)
linux linux_kernel From 6.16 (inc) to 6.16.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-NVD-CWE-noinfo
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs in the Linux kernel's perf subsystem, specifically in the perf_mmap() function. When a buffer is allocated or attached, perf_mmap() tries to map it read-only into the page table. If this mapping fails, the function cleans up some page table entries but does not properly handle other side effects, such as updating reference counts and user memory accounting. This leads to leaked reference counts, corrupted user memory accounting, and unbalanced event mapping calls. The fix involves reordering calls so that on failure, cleanup functions are properly invoked to avoid these issues.


How can this vulnerability impact me? :

This vulnerability can cause resource leaks and corruption in the kernel's memory accounting related to performance monitoring buffers. Specifically, leaked reference counts and corrupted user memory accounting can lead to instability or unexpected behavior in the system. Additionally, unbalanced event mapping calls may cause further inconsistencies in performance event handling, potentially affecting system reliability or security.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart