CVE-2025-38565: Linux kernel · perf/core: Exit early on perf_mmap() fail
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f41e9eba77bf97626e04296dc5677d02816d2432 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in f41e9eba77bf97626e04296dc5677d02816d2432, de85e72598d89880a02170a1cbc27b35a7d978a9, 92043120a2e992800580855498ab8507e1b22db9 +6
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: perf/core: Exit early on perf_mmap() fail When perf_mmap() fails to allocate a buffer, it still invokes the event_mapped() callback of the related event. On X86 this might increase the perf_rdpmc_allowed reference counter. But nothing undoes this as perf_mmap_close() is never called in this case, which causes another reference count leak. Return early on failure to prevent that.
References
- git.kernel.org/stable/c/5ffda7f3ed76ec8defc19d985e33b3b82ba07839 (opens in a new tab)
- git.kernel.org/stable/c/9b90a48c7de828a15c7a4fc565d46999c6e22d6b (opens in a new tab)
- git.kernel.org/stable/c/de85e72598d89880a02170a1cbc27b35a7d978a9 (opens in a new tab)
- git.kernel.org/stable/c/27d44145bd576bbef9bf6165bcd78128ec3e6cbd (opens in a new tab)
- git.kernel.org/stable/c/f41e9eba77bf97626e04296dc5677d02816d2432 (opens in a new tab)
- git.kernel.org/stable/c/92043120a2e992800580855498ab8507e1b22db9 (opens in a new tab)
- git.kernel.org/stable/c/163b0d1a209fe0df5476c1df2330ca12b55abf92 (opens in a new tab)
- git.kernel.org/stable/c/7ff8521f30c4c2fcd4e88bd7640486602bf8a650 (opens in a new tab)
- git.kernel.org/stable/c/07091aade394f690e7b655578140ef84d0e8d7b0 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html (opens in a new tab)