LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-48713 is a Linux kernel crash bug in Intel Processor Trace handling. When a configured PT stop filter is hit in single-range mode, the kernel can dereference a null pointer and crash. This is primarily an availability risk for systems where Intel PT tracing via perf is available and used.

Executive priority

Treat as a maintenance-priority kernel availability issue. Patch affected Linux fleets through normal expedited kernel update processes, especially performance-monitoring, developer, and observability systems using perf tracing.

Technical view

The bug is in perf/x86/intel/pt. A missing !buf->single check allows pt_buffer_region_size to be called without a ToPA buffer configured. The issue was introduced by commit 670638477aed and is fixed by stable kernel commits referenced by the CVE record.

Likely exposure

Exposure is most likely on Linux systems with affected kernel builds, Intel PT support, and users or workloads permitted to use perf PT tracing with stop filters. The source does not identify remote exposure.

Exploitation context

The source describes a reproducible kernel crash when PT recording hits a stop filter. CISA KEV is false in the provided bundle, and no cited source reports active exploitation.

Researcher notes

Evidence is limited to the kernel fix description and CVE metadata. Severity, CVSS, CWE, and exploitability details are not provided. Avoid assuming privilege requirements beyond the apparent need to trigger perf Intel PT tracing behavior.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable fixes.
  • Prioritize hosts where perf Intel PT tracing is enabled or used.
  • If updates are delayed, check vendor guidance for safe temporary controls.

Validation and detection

  • Inventory Linux kernel versions and compare with vendor fixed releases.
  • Confirm whether the kernel includes one of the referenced stable commits.
  • Identify systems using Intel PT tracing or perf-based profiling.
  • Review crash reports for Intel PT or perf-related null pointer dereferences.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-48713 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux670638477aede0d7a355ced04b569214aa3feacd, 670638477aede0d7a355ced04b569214aa3feacd, 670638477aede0d7a355ced04b569214aa3feacd, 670638477aede0d7a355ced04b569214aa3feacdunaffected
LinuxLinux5.5, 0, 5.10.99, 5.15.22, 5.16.8, 5.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.