Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38563perf/core: Prevent VMA split of buffer mappings

Description

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 perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() 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 vm_operations_struct::may_split() 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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38563, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.44% · top 61% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < e4346ffec2c44d6b0be834d59b20632b5bb5729e
    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < d52451a9210f2e5a079ba052918c93563518a9ff
    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < 3bd518cc7ea61076bcd725e36ff0e690754977c0
    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < 7b84cb58d1f0aa07656802eae24689566e5f5b1b
    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < 6757a31a8e295ae4f01717a954afda173f25a121
    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < e529888b7e8092912dd8789bdfc76685ccd2ff5f
    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < ff668930871e0198c7f4e325058b8b7c286787bd
    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < 65311aad4c808bedad0c05d9bb8b06c47dae73eb
    • affected 45bfb2e50471abbbfd83d40d28c986078b0d24ff – < b024d7b56c77191cde544f838debb7f8451cd0d6
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • unaffected 5.4.297 – ≤ 5.4.*
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.148 – ≤ 6.1.*
    • unaffected 6.6.102 – ≤ 6.6.*
    • unaffected 6.12.42 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References12

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38563 badge
[![CVE-2025-38563](https://cveledger.app/badge/CVE-2025-38563.svg)](https://cveledger.app/cve/CVE-2025-38563)

Record last updated .