<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-29T23:26:01.889974+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-83qv-jr76-p4xc</id>
    <title>GHSA-83qv-jr76-p4xc</title>
    <updated>2026-10-29T23:26:01.922396+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>s390/pai: Handle multiple PMU stop callback invocations</p>
<p>Handle the following scenario:
The kernel protects itself against a very high sampling load and
throttles the sampling using:</p>
<p>perf_event_throttle() --&gt; PMU-&gt;stop()</p>
<p>Shortly later the scheduler may terminate the task and removes it from the
CPU. It again calls</p>
<p>PMU-&gt;stop()</p>
<p>which results in two invocations of PMU-&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-&gt;start().</p>
<p>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.</p>
<p>Use list_for_each_entry_safe() for safe iteration over syswide_list
in pai_have_samples().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-83qv-jr76-p4xc"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-99125</id>
    <title>UBUNTU-CVE-2026-99125</title>
    <updated>2026-10-29T23:26:01.922488+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: s390/pai: Handle multiple PMU stop callback invocations Handle the following scenario: The kernel protects itself against a very high sampling load and throttles the sampling using:   perf_event_throttle() --&gt; PMU-&gt;stop() Shortly later the scheduler may terminate the task and removes it from the CPU. It again calls   PMU-&gt;stop() which results in two invocations of PMU-&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-&gt;start(). 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. Use list_for_each_entry_safe() for safe iteration over syswide_list in pai_have_samples().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-99125"/>
  </entry>
</feed>
