Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-48713

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

Medium5.5EPSS 0.25%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2022-48713, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected 670638477aede0d7a355ced04b569214aa3feacd – < 456f041e035913fcedb275aff6f8a71dfebcd394
    • affected 670638477aede0d7a355ced04b569214aa3feacd – < e83d941fd3445f660d2f43647c580a320cc384f6
    • affected 670638477aede0d7a355ced04b569214aa3feacd – < feffb6ae2c80b9a8206450cdef90f5943baced99
    • affected 670638477aede0d7a355ced04b569214aa3feacd – < 1d9093457b243061a9bba23543c38726e864a643
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.99 – ≤ 5.10.*
    • unaffected 5.15.22 – ≤ 5.15.*
    • unaffected 5.16.8 – ≤ 5.16.*
    • unaffected 5.17 – ≤ *

References (4)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48713 badge
[![CVE-2022-48713](https://trackcve.app/badge/CVE-2022-48713.svg)](https://trackcve.app/cve/CVE-2022-48713)

Record last updated .