<?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, 09 Nov 2026 17:25:03 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1473 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1473</link>
      <description>certfr-2026-avi-1473</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1473</guid>
    </item>
    <item>
      <title>fkie_cve-2026-99187</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99187</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf: Fix perf_pmu_migrate_context() leaving events behind&lt;/p&gt;
&lt;p&gt;__perf_pmu_remove() walks the group leaders of a CPU and PMU with
perf_event_groups_for_cpu_pmu(), removing each one as it goes.
perf_remove_from_context() takes the leader out of the groups rbtree,
after which rb_next() on that node returns NULL, prematurely ending the
walk. Other groups stay behind in the source context.&lt;/p&gt;
&lt;p&gt;On CPU hotplug, they are then torn down with the dying CPU. They keep
running until teardown, while the PMU&amp;#39;s interrupt and migrated events
are on a new CPU, which drivers rely on never happening.&lt;/p&gt;
&lt;p&gt;Walk ctx-&amp;gt;event_list instead and pick out the PMU&amp;#39;s events by their
pmu_ctx.&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 perf_pmu_migrate_context() leaving events behind&lt;/p&gt;
&lt;p&gt;__perf_pmu_remove() walks the group leaders of a CPU and PMU with
perf_event_groups_for_cpu_pmu(), removing each one as it goes.
perf_remove_from_context() takes the leader out of the groups rbtree,
after which rb_next() on that node returns NULL, prematurely ending the
walk. Other groups stay behind in the source context.&lt;/p&gt;
&lt;p&gt;On CPU hotplug, they are then torn down with the dying CPU. They keep
running until teardown, while the PMU&amp;#39;s interrupt and migrated events
are on a new CPU, which drivers rely on never happening.&lt;/p&gt;
&lt;p&gt;Walk ctx-&amp;gt;event_list instead and pick out the PMU&amp;#39;s events by their
pmu_ctx.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99187</guid>
    </item>
    <item>
      <title>GHSA-29rh-rvqr-jrpj</title>
      <link>https://db.gcve.eu/vuln/ghsa-29rh-rvqr-jrpj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;perf: Fix perf_pmu_migrate_context() leaving events behind&lt;/p&gt;
&lt;p&gt;__perf_pmu_remove() walks the group leaders of a CPU and PMU with
perf_event_groups_for_cpu_pmu(), removing each one as it goes.
perf_remove_from_context() takes the leader out of the groups rbtree,
after which rb_next() on that node returns NULL, prematurely ending the
walk. Other groups stay behind in the source context.&lt;/p&gt;
&lt;p&gt;On CPU hotplug, they are then torn down with the dying CPU. They keep
running until teardown, while the PMU&amp;#39;s interrupt and migrated events
are on a new CPU, which drivers rely on never happening.&lt;/p&gt;
&lt;p&gt;Walk ctx-&amp;gt;event_list instead and pick out the PMU&amp;#39;s events by their
pmu_ctx.&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 perf_pmu_migrate_context() leaving events behind&lt;/p&gt;
&lt;p&gt;__perf_pmu_remove() walks the group leaders of a CPU and PMU with
perf_event_groups_for_cpu_pmu(), removing each one as it goes.
perf_remove_from_context() takes the leader out of the groups rbtree,
after which rb_next() on that node returns NULL, prematurely ending the
walk. Other groups stay behind in the source context.&lt;/p&gt;
&lt;p&gt;On CPU hotplug, they are then torn down with the dying CPU. They keep
running until teardown, while the PMU&amp;#39;s interrupt and migrated events
are on a new CPU, which drivers rely on never happening.&lt;/p&gt;
&lt;p&gt;Walk ctx-&amp;gt;event_list instead and pick out the PMU&amp;#39;s events by their
pmu_ctx.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-29rh-rvqr-jrpj</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99187 — perf: Fix perf_pmu_migrate_context() leaving events behind</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99187</link>
      <description>msrc_CVE-2026-99187</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99187</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99187</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99187</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 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pmu_migrate_context() leaving events behind __perf_pmu_remove() walks the group leaders of a CPU and PMU with perf_event_groups_for_cpu_pmu(), removing each one as it goes. perf_remove_from_context() takes the leader out of the groups rbtree, after which rb_next() on that node returns NULL, prematurely ending the walk. Other groups stay behind in the source context. On CPU hotplug, they are then torn down with the dying CPU. They keep running until teardown, while the PMU&amp;#39;s interrupt and migrated events are on a new CPU, which drivers rely on never happening. Walk ctx-&amp;gt;event_list instead and pick out the PMU&amp;#39;s events by their pmu_ctx.&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 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pmu_migrate_context() leaving events behind __perf_pmu_remove() walks the group leaders of a CPU and PMU with perf_event_groups_for_cpu_pmu(), removing each one as it goes. perf_remove_from_context() takes the leader out of the groups rbtree, after which rb_next() on that node returns NULL, prematurely ending the walk. Other groups stay behind in the source context. On CPU hotplug, they are then torn down with the dying CPU. They keep running until teardown, while the PMU&amp;#39;s interrupt and migrated events are on a new CPU, which drivers rely on never happening. Walk ctx-&amp;gt;event_list instead and pick out the PMU&amp;#39;s events by their pmu_ctx.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99187</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4224 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4224</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-4224</guid>
    </item>
  </channel>
</rss>
