CVE-2022-48713
Linux Kernel perf/x86/intel/pt Null Pointer Dereference Crash
Description
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 pt_buffer_region_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 pt_handle_status due to calling pt_buffer_region_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.
INFO
Published Date :
June 20, 2024, 11:15 a.m.
Last Modified :
Nov. 21, 2024, 7:33 a.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-48713.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-48713 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-48713 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/1d9093457b243061a9bba23543c38726e864a643 Added Reference https://git.kernel.org/stable/c/456f041e035913fcedb275aff6f8a71dfebcd394 Added Reference https://git.kernel.org/stable/c/e83d941fd3445f660d2f43647c580a320cc384f6 Added Reference https://git.kernel.org/stable/c/feffb6ae2c80b9a8206450cdef90f5943baced99 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 20, 2024
Action Type Old Value New Value Added Description 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 pt_buffer_region_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 pt_handle_status due to calling pt_buffer_region_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. Added Reference kernel.org https://git.kernel.org/stable/c/456f041e035913fcedb275aff6f8a71dfebcd394 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e83d941fd3445f660d2f43647c580a320cc384f6 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/feffb6ae2c80b9a8206450cdef90f5943baced99 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/1d9093457b243061a9bba23543c38726e864a643 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-48713 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-48713
weaknesses.