<?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://db.gcve.eu</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>Thu, 29 Oct 2026 13:30:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99125 — s390/pai: Handle multiple PMU stop callback invocations</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99125</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;s390/pai: Handle multiple PMU stop callback invocations&lt;/p&gt;
&lt;p&gt;Handle the following scenario:
The kernel protects itself against a very high sampling load and
throttles the sampling using:&lt;/p&gt;
&lt;p&gt;perf_event_throttle() --&amp;gt; PMU-&amp;gt;stop()&lt;/p&gt;
&lt;p&gt;Shortly later the scheduler may terminate the task and removes it from the
CPU. It again calls&lt;/p&gt;
&lt;p&gt;PMU-&amp;gt;stop()&lt;/p&gt;
&lt;p&gt;which results in two invocations of PMU-&amp;gt;stop() called back to back.
Protect against this and check the PERF_HES_STOPPED bit on function
entry.  If it is already set return.
Clear bit PERF_HES_STOPPED in PMU-&amp;gt;start().&lt;/p&gt;
&lt;p&gt;Prohibit ioctl(fd, PERF_EVENT_IOC_PERIOD, ...) call for this event.
It sets perf_event::event_limit to a positive value and causes
perf_event_overflow() to invoke pai_stop() call back function when
perf_event::event_limit hits zero. This is not supported because the
sample events CRYPTO_ALL and NNPA_ALL are only taken at schedule out
of a task.&lt;/p&gt;
&lt;p&gt;Use list_for_each_entry_safe() for safe iteration over syswide_list
in pai_have_samples().&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;s390/pai: Handle multiple PMU stop callback invocations&lt;/p&gt;
&lt;p&gt;Handle the following scenario:
The kernel protects itself against a very high sampling load and
throttles the sampling using:&lt;/p&gt;
&lt;p&gt;perf_event_throttle() --&amp;gt; PMU-&amp;gt;stop()&lt;/p&gt;
&lt;p&gt;Shortly later the scheduler may terminate the task and removes it from the
CPU. It again calls&lt;/p&gt;
&lt;p&gt;PMU-&amp;gt;stop()&lt;/p&gt;
&lt;p&gt;which results in two invocations of PMU-&amp;gt;stop() called back to back.
Protect against this and check the PERF_HES_STOPPED bit on function
entry.  If it is already set return.
Clear bit PERF_HES_STOPPED in PMU-&amp;gt;start().&lt;/p&gt;
&lt;p&gt;Prohibit ioctl(fd, PERF_EVENT_IOC_PERIOD, ...) call for this event.
It sets perf_event::event_limit to a positive value and causes
perf_event_overflow() to invoke pai_stop() call back function when
perf_event::event_limit hits zero. This is not supported because the
sample events CRYPTO_ALL and NNPA_ALL are only taken at schedule out
of a task.&lt;/p&gt;
&lt;p&gt;Use list_for_each_entry_safe() for safe iteration over syswide_list
in pai_have_samples().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99125</guid>
    </item>
  </channel>
</rss>
