<?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>Tue, 03 Nov 2026 10:30:58 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98788</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98788</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;futex: Fix private hash use-after-free on resize&lt;/p&gt;
&lt;p&gt;poll_state_synchronize_rcu(mm-&amp;gt;futex.phash.batches) is used by
futex_ref_drop() to check that a grace period has passed since the
current hash was published. This relies on batches referencing a grace
period which started after the hash pointer was assigned.&lt;/p&gt;
&lt;p&gt;__futex_pivot_hash() sets mmph-&amp;gt;batches before it replaces mmph-&amp;gt;hash:&lt;/p&gt;
&lt;p&gt;scoped_guard(rcu) {
            mmph-&amp;gt;batches = get_state_synchronize_rcu();
            rcu_assign_pointer(mmph-&amp;gt;hash, new);
    }&lt;/p&gt;
&lt;p&gt;The scoped_guard(rcu) doesn&amp;#39;t stop new grace periods from starting, and
if one starts between those two assignments, futex_ref_drop() can move
forward while a reader still holds a pointer to the old hash.&lt;/p&gt;
&lt;p&gt;Fix things by setting mmph-&amp;gt;batches after assigning mmph-&amp;gt;hash.  The
scoped_guard(rcu) isn&amp;#39;t needed, so let&amp;#39;s drop that as well.&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;futex: Fix private hash use-after-free on resize&lt;/p&gt;
&lt;p&gt;poll_state_synchronize_rcu(mm-&amp;gt;futex.phash.batches) is used by
futex_ref_drop() to check that a grace period has passed since the
current hash was published. This relies on batches referencing a grace
period which started after the hash pointer was assigned.&lt;/p&gt;
&lt;p&gt;__futex_pivot_hash() sets mmph-&amp;gt;batches before it replaces mmph-&amp;gt;hash:&lt;/p&gt;
&lt;p&gt;scoped_guard(rcu) {
            mmph-&amp;gt;batches = get_state_synchronize_rcu();
            rcu_assign_pointer(mmph-&amp;gt;hash, new);
    }&lt;/p&gt;
&lt;p&gt;The scoped_guard(rcu) doesn&amp;#39;t stop new grace periods from starting, and
if one starts between those two assignments, futex_ref_drop() can move
forward while a reader still holds a pointer to the old hash.&lt;/p&gt;
&lt;p&gt;Fix things by setting mmph-&amp;gt;batches after assigning mmph-&amp;gt;hash.  The
scoped_guard(rcu) isn&amp;#39;t needed, so let&amp;#39;s drop that as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98788</guid>
    </item>
    <item>
      <title>GHSA-qwmc-gmgx-xf8h</title>
      <link>https://db.gcve.eu/vuln/ghsa-qwmc-gmgx-xf8h</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;futex: Fix private hash use-after-free on resize&lt;/p&gt;
&lt;p&gt;poll_state_synchronize_rcu(mm-&amp;gt;futex.phash.batches) is used by
futex_ref_drop() to check that a grace period has passed since the
current hash was published. This relies on batches referencing a grace
period which started after the hash pointer was assigned.&lt;/p&gt;
&lt;p&gt;__futex_pivot_hash() sets mmph-&amp;gt;batches before it replaces mmph-&amp;gt;hash:&lt;/p&gt;
&lt;p&gt;scoped_guard(rcu) {
            mmph-&amp;gt;batches = get_state_synchronize_rcu();
            rcu_assign_pointer(mmph-&amp;gt;hash, new);
    }&lt;/p&gt;
&lt;p&gt;The scoped_guard(rcu) doesn&amp;#39;t stop new grace periods from starting, and
if one starts between those two assignments, futex_ref_drop() can move
forward while a reader still holds a pointer to the old hash.&lt;/p&gt;
&lt;p&gt;Fix things by setting mmph-&amp;gt;batches after assigning mmph-&amp;gt;hash.  The
scoped_guard(rcu) isn&amp;#39;t needed, so let&amp;#39;s drop that as well.&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;futex: Fix private hash use-after-free on resize&lt;/p&gt;
&lt;p&gt;poll_state_synchronize_rcu(mm-&amp;gt;futex.phash.batches) is used by
futex_ref_drop() to check that a grace period has passed since the
current hash was published. This relies on batches referencing a grace
period which started after the hash pointer was assigned.&lt;/p&gt;
&lt;p&gt;__futex_pivot_hash() sets mmph-&amp;gt;batches before it replaces mmph-&amp;gt;hash:&lt;/p&gt;
&lt;p&gt;scoped_guard(rcu) {
            mmph-&amp;gt;batches = get_state_synchronize_rcu();
            rcu_assign_pointer(mmph-&amp;gt;hash, new);
    }&lt;/p&gt;
&lt;p&gt;The scoped_guard(rcu) doesn&amp;#39;t stop new grace periods from starting, and
if one starts between those two assignments, futex_ref_drop() can move
forward while a reader still holds a pointer to the old hash.&lt;/p&gt;
&lt;p&gt;Fix things by setting mmph-&amp;gt;batches after assigning mmph-&amp;gt;hash.  The
scoped_guard(rcu) isn&amp;#39;t needed, so let&amp;#39;s drop that as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qwmc-gmgx-xf8h</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98788 — futex: Fix private hash use-after-free on resize</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98788</link>
      <description>msrc_CVE-2026-98788</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98788</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98788</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98788</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: futex: Fix private hash use-after-free on resize poll_state_synchronize_rcu(mm-&amp;gt;futex.phash.batches) is used by futex_ref_drop() to check that a grace period has passed since the current hash was published. This relies on batches referencing a grace period which started after the hash pointer was assigned. __futex_pivot_hash() sets mmph-&amp;gt;batches before it replaces mmph-&amp;gt;hash:     scoped_guard(rcu) {             mmph-&amp;gt;batches = get_state_synchronize_rcu();             rcu_assign_pointer(mmph-&amp;gt;hash, new);     } The scoped_guard(rcu) doesn&amp;#39;t stop new grace periods from starting, and if one starts between those two assignments, futex_ref_drop() can move forward while a reader still holds a pointer to the old hash. Fix things by setting mmph-&amp;gt;batches after assigning mmph-&amp;gt;hash.  The scoped_guard(rcu) isn&amp;#39;t needed, so let&amp;#39;s drop that as well.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: futex: Fix private hash use-after-free on resize poll_state_synchronize_rcu(mm-&amp;gt;futex.phash.batches) is used by futex_ref_drop() to check that a grace period has passed since the current hash was published. This relies on batches referencing a grace period which started after the hash pointer was assigned. __futex_pivot_hash() sets mmph-&amp;gt;batches before it replaces mmph-&amp;gt;hash:     scoped_guard(rcu) {             mmph-&amp;gt;batches = get_state_synchronize_rcu();             rcu_assign_pointer(mmph-&amp;gt;hash, new);     } The scoped_guard(rcu) doesn&amp;#39;t stop new grace periods from starting, and if one starts between those two assignments, futex_ref_drop() can move forward while a reader still holds a pointer to the old hash. Fix things by setting mmph-&amp;gt;batches after assigning mmph-&amp;gt;hash.  The scoped_guard(rcu) isn&amp;#39;t needed, so let&amp;#39;s drop that as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98788</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>
