<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 19:26:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48713 — perf/x86/intel/pt: Fix crash with stop filters in single-range mode</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-48713</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/intel/pt: Fix crash with stop filters in single-range mode&lt;/p&gt;
&lt;p&gt;Add a check for !buf-&amp;gt;single before calling pt_buffer_region_size in a
place where a missing check can cause a kernel crash.&lt;/p&gt;
&lt;p&gt;Fixes a bug introduced by commit 670638477aed (&amp;#34;perf/x86/intel/pt:
Opportunistically use single range output mode&amp;#34;), 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.&lt;/p&gt;
&lt;p&gt;The commit which introduced single-range mode guarded almost all uses of
the ToPA buffer variables with checks of the buf-&amp;gt;single variable, but
missed the case where tracing was stopped by the PT hardware, which
happens when execution hits a configured stop filter.&lt;/p&gt;
&lt;p&gt;Tested that hitting a stop filter while PT recording successfully
records a trace with this patch but crashes without this patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf/x86/intel/pt: Fix crash with stop filters in single-range mode&lt;/p&gt;
&lt;p&gt;Add a check for !buf-&amp;gt;single before calling pt_buffer_region_size in a
place where a missing check can cause a kernel crash.&lt;/p&gt;
&lt;p&gt;Fixes a bug introduced by commit 670638477aed (&amp;#34;perf/x86/intel/pt:
Opportunistically use single range output mode&amp;#34;), 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.&lt;/p&gt;
&lt;p&gt;The commit which introduced single-range mode guarded almost all uses of
the ToPA buffer variables with checks of the buf-&amp;gt;single variable, but
missed the case where tracing was stopped by the PT hardware, which
happens when execution hits a configured stop filter.&lt;/p&gt;
&lt;p&gt;Tested that hitting a stop filter while PT recording successfully
records a trace with this patch but crashes without this patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-48713</guid>
    </item>
  </channel>
</rss>
