Performance-counter exposure via failed mmap callback
Published Aug 19, 2025 · Updated May 11, 2026
A reference-count leak in Linux perf/core allows local users to retain x86 RDPMC access after a perf mmap allocation fails. perf_mmap() calls event_mapped() after buffer allocation failure, incrementing perf_rdpmc_allowed without a matching perf_mmap_close() decrement. Triggering the flaw requires local low-privileged access and an x86 system; the leak can leave RDPMC access enabled beyond the failed mapping.
Summary
What happened
A reference-count leak in Linux perf/core allows local users to retain x86 RDPMC access after a perf mmap allocation fails. perf_mmap() calls event_mapped() after buffer allocation failure, incrementing perf_rdpmc_allowed without a matching perf_mmap_close() decrement. Triggering the flaw requires local low-privileged access and an x86 system; the leak can leave RDPMC access enabled beyond the failed mapping.
The record
- CVE
- CVE-2025-38565
- Published
- Aug 19, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <07091aade394f690e7b655578140ef84d0e8d7b0
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <163b0d1a209fe0df5476c1df2330ca12b55abf92
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <27d44145bd576bbef9bf6165bcd78128ec3e6cbd
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <5ffda7f3ed76ec8defc19d985e33b3b82ba07839
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <7ff8521f30c4c2fcd4e88bd7640486602bf8a650
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <92043120a2e992800580855498ab8507e1b22db9
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <9b90a48c7de828a15c7a4fc565d46999c6e22d6b
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <de85e72598d89880a02170a1cbc27b35a7d978a9
- Affected versionversion=1e0fb9ec679c9273a641f1d6f3d25ea47baef2bb <f41e9eba77bf97626e04296dc5677d02816d2432
- Affected versionversion=4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo