CVE-2025-38055
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel occurs in the perf subsystem for Intel CPUs when using PEBS-via-PT with a sample frequency instead of a sample period. It causes a kernel NULL pointer dereference (segfault) because the function intel_pmu_pebs_event_update_no_drain() incorrectly assumes all pebs_enabled bits represent counter indexes, which is not true for bits 60 and 61 used by PEBS-via-PT. This leads to a crash when handling performance monitoring interrupts.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash (segfault) when using PEBS-via-PT with sample frequency, leading to system instability or downtime. This could disrupt normal operations on affected systems, especially those relying on performance monitoring features.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel crash logs or oops messages indicating a NULL pointer dereference related to perf events, specifically with PEBS-via-PT and sample frequency usage. Look for kernel messages similar to: 'BUG: kernel NULL pointer dereference, address: 0000000000000195' and stack traces involving 'intel_pmu_pebs_event_update_no_drain'. There are no specific commands provided to detect this vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the patch that fixes the intel_pmu_pebs_event_update_no_drain() function to correctly handle PEBS-via-PT with sample frequency. Until the fix is applied, avoid using PEBS-via-PT with sample frequency settings to prevent kernel crashes.