CVE-2022-48713

perf/x86/intel/pt: Fix crash with stop filters in single-range mode

MEDIUM
5.5
CVSS Score
Published: June 20, 2024 at 11:13 AM UTC
Updated: June 17, 2026 at 05:15 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.15.225.16 ≤ v < 5.16.85.5 ≤ v < 5.10.995.5 ≤ v < 5.15.225.5 ≤ v < 5.16.85.5 ≤ v < 5.175.17 rc15.17 rc25.5670638477aede0d7a355ced04b569214aa3feacd
Vendor states this is fixed in 1d9093457b243061a9bba23543c38726e864a643 (fixed)
Vendor states this is fixed in 456f041e035913fcedb275aff6f8a71dfebcd394 (fixed)
Vendor states this is fixed in e83d941fd3445f660d2f43647c580a320cc384f6 (fixed)
Vendor states this is fixed in feffb6ae2c80b9a8206450cdef90f5943baced99 (fixed)
Vendor states this is fixed in 5.10.99 (unaffected)
Vendor states this is fixed in 5.15.22 (unaffected)
Vendor states this is fixed in 5.16.8 (unaffected)
Vendor states this is fixed in 5.17 (unaffected)
Vendor states this is fixed in 5.5 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1d9093457b243061a9bba23543c38726e864a643
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/456f041e035913fcedb275aff6f8a71dfebcd394
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e83d941fd3445f660d2f43647c580a320cc384f6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/feffb6ae2c80b9a8206450cdef90f5943baced99

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card