<?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>Mon, 02 Nov 2026 23:09:12 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98790</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98790</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf: Fix race between perf_event_exit_task() and perf_pending_task()&lt;/p&gt;
&lt;p&gt;A race condition exists between perf_event_exit_task() and
perf_pending_task() during begin_new_exec().&lt;/p&gt;
&lt;p&gt;During begin_new_exec(), perf_event_exit_task() may be called, and the
PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute
and triggers WARN_ON_ONCE(event-&amp;gt;ctx-&amp;gt;task != current).&lt;/p&gt;
&lt;p&gt;Since both task exit and exec paths can call perf_event_exit_task() which
sets ctx-&amp;gt;task to TASK_TOMBSTONE, fix this by explicitly checking if
event-&amp;gt;ctx-&amp;gt;task equals TASK_TOMBSTONE and dropping the redundant
PF_EXITING check.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf: Fix race between perf_event_exit_task() and perf_pending_task()&lt;/p&gt;
&lt;p&gt;A race condition exists between perf_event_exit_task() and
perf_pending_task() during begin_new_exec().&lt;/p&gt;
&lt;p&gt;During begin_new_exec(), perf_event_exit_task() may be called, and the
PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute
and triggers WARN_ON_ONCE(event-&amp;gt;ctx-&amp;gt;task != current).&lt;/p&gt;
&lt;p&gt;Since both task exit and exec paths can call perf_event_exit_task() which
sets ctx-&amp;gt;task to TASK_TOMBSTONE, fix this by explicitly checking if
event-&amp;gt;ctx-&amp;gt;task equals TASK_TOMBSTONE and dropping the redundant
PF_EXITING check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98790</guid>
    </item>
    <item>
      <title>GHSA-hx5j-phv4-m97w</title>
      <link>https://db.gcve.eu/vuln/ghsa-hx5j-phv4-m97w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf: Fix race between perf_event_exit_task() and perf_pending_task()&lt;/p&gt;
&lt;p&gt;A race condition exists between perf_event_exit_task() and
perf_pending_task() during begin_new_exec().&lt;/p&gt;
&lt;p&gt;During begin_new_exec(), perf_event_exit_task() may be called, and the
PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute
and triggers WARN_ON_ONCE(event-&amp;gt;ctx-&amp;gt;task != current).&lt;/p&gt;
&lt;p&gt;Since both task exit and exec paths can call perf_event_exit_task() which
sets ctx-&amp;gt;task to TASK_TOMBSTONE, fix this by explicitly checking if
event-&amp;gt;ctx-&amp;gt;task equals TASK_TOMBSTONE and dropping the redundant
PF_EXITING check.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf: Fix race between perf_event_exit_task() and perf_pending_task()&lt;/p&gt;
&lt;p&gt;A race condition exists between perf_event_exit_task() and
perf_pending_task() during begin_new_exec().&lt;/p&gt;
&lt;p&gt;During begin_new_exec(), perf_event_exit_task() may be called, and the
PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute
and triggers WARN_ON_ONCE(event-&amp;gt;ctx-&amp;gt;task != current).&lt;/p&gt;
&lt;p&gt;Since both task exit and exec paths can call perf_event_exit_task() which
sets ctx-&amp;gt;task to TASK_TOMBSTONE, fix this by explicitly checking if
event-&amp;gt;ctx-&amp;gt;task equals TASK_TOMBSTONE and dropping the redundant
PF_EXITING check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-hx5j-phv4-m97w</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98790 — perf: Fix race between perf_event_exit_task() and perf_pending_task()</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98790</link>
      <description>msrc_CVE-2026-98790</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98790</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98790</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98790</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf: Fix race between perf_event_exit_task() and perf_pending_task() A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec(). During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event-&amp;gt;ctx-&amp;gt;task != current). Since both task exit and exec paths can call perf_event_exit_task() which sets ctx-&amp;gt;task to TASK_TOMBSTONE, fix this by explicitly checking if event-&amp;gt;ctx-&amp;gt;task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf: Fix race between perf_event_exit_task() and perf_pending_task() A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec(). During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event-&amp;gt;ctx-&amp;gt;task != current). Since both task exit and exec paths can call perf_event_exit_task() which sets ctx-&amp;gt;task to TASK_TOMBSTONE, fix this by explicitly checking if event-&amp;gt;ctx-&amp;gt;task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98790</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4019</guid>
    </item>
  </channel>
</rss>
