CVE-2025-38055
perf/x86/intel: Fix segfault with PEBS-via-PT with sample_freq
Reported by linux · Published June 18, 2025
In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel: Fix segfault with PEBS-via-PT with sample_freq Currently, using PEBS-via-PT with a sample frequency instead of a sample period, causes a segfault. For example: BUG: kernel NULL pointer dereference, address: 0000000000000195 <NMI> ? __die_body.cold+0x19/0x27 ? page_fault_oops+0xca/0x290 ? exc_page_fault+0x7e/0x1b0 ? asm_exc_page_fault+0x26/0x30 ? intel_pmu_pebs_event_update_no_drain+0x40/0x60 ? intel_pmu_pebs_event_update_no_drain+0x32/0x60 intel_pmu_drain_pebs_icl+0x333/0x350 handle_pmi_common+0x272/0x3c0 intel_pmu_handle_irq+0x10a/0x2e0 perf_event_nmi_handler+0x2a/0x50 That happens because intel_pmu_pebs_event_update_no_drain() assumes all the pebs_enabled bits represent counter indexes, which is not always the case. In this particular case, bits 60 and 61 are set for PEBS-via-PT purposes. The behaviour of PEBS-via-PT with sample frequency is questionable because although a PMI is generated (PEBS_PMI_AFTER_EACH_RECORD), the period is not adjusted anyway. Putting that aside, fix intel_pmu_pebs_event_update_no_drain() by passing the mask of counter bits instead of 'size'. Note, prior to the Fixes commit, 'size' would be limited to the maximum counter index, so the issue was not hit.
EPSS 0.20% · 9.7th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12-modules-extra | Amazon Linux | 6.12.31-35.92.amzn2023 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 722e42e45c2f1c6d1adec7813651dba5139f52f4, 722e42e45c2f1c6d1adec7813651dba5139f52f4, 722e42e45c2f1c6d1adec7813651dba5139f52f4 |
| Linux | Linux | 6.11, 0, 6.12.31 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| Linux | Linux | 6.10.5, *, 722e42e45c2f1c6d1adec7813651dba5139f52f4 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| linux | linux_kernel | 6.10.5, 6.11, 6.11 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel-livepatch-6.12.31-35.92 | 0 |
Timeline
- Jun 17, 2025 CVE Published
- Jun 18, 2025 EPSS Score (30 in total, the first dated here)
- Jun 18, 2025 Coalition ESS Score (19 in total, the first dated here)
- Dec 15, 2025 Security Advisory (311 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (299 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38055
vulnetix vdb fixes CVE-2025-38055
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38055/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart