CVE-2022-48713
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2022-48713
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-48713.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2022-48713
- Downstream
- Related
- Published
- 2024-06-20T11:15:54Z
- Modified
- 2025-09-17T17:12:38Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- [none]
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
perf/x86/intel/pt: Fix crash with stop filters in single-range mode
Add a check for !buf->single before calling ptbufferregion_size in a place where a missing check can cause a kernel crash.
Fixes a bug introduced by commit 670638477aed ("perf/x86/intel/pt: Opportunistically use single range output mode"), which added a support for PT single-range output mode. Since that commit if a PT stop filter range is hit while tracing, the kernel will crash because of a null pointer dereference in pthandlestatus due to calling ptbufferregion_size without a ToPA configured.
The commit which introduced single-range mode guarded almost all uses of the ToPA buffer variables with checks of the buf->single variable, but missed the case where tracing was stopped by the PT hardware, which happens when execution hits a configured stop filter.
Tested that hitting a stop filter while PT recording successfully records a trace with this patch but crashes without this patch.
- References