<?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>Fri, 20 Nov 2026 21:30:19 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99731</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99731</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/filemap: don&amp;#39;t lose a folio lock wakeup to a signal&lt;/p&gt;
&lt;p&gt;An exclusive waiter in folio_wait_bit_common() can leave the wait loop
because of a fatal signal, then be woken by folio_unlock() before
finish_wait(). If the waker did not hand over the lock, the waiter returns
-EINTR without trying to acquire it.&lt;/p&gt;
&lt;p&gt;folio_wake_bit() stops after waking the first exclusive waiter, so this
loses the wakeup and can leave other waiters asleep indefinitely on an
unlocked folio.&lt;/p&gt;
&lt;p&gt;After finish_wait(), let a waiter woken without a lock handoff try once
more to acquire the lock. If successful, return success so the caller&amp;#39;s
eventual unlock wakes the next waiter. Otherwise, the current lock owner
will do so.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: clarify and simplify comment + description ]&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;mm/filemap: don&amp;#39;t lose a folio lock wakeup to a signal&lt;/p&gt;
&lt;p&gt;An exclusive waiter in folio_wait_bit_common() can leave the wait loop
because of a fatal signal, then be woken by folio_unlock() before
finish_wait(). If the waker did not hand over the lock, the waiter returns
-EINTR without trying to acquire it.&lt;/p&gt;
&lt;p&gt;folio_wake_bit() stops after waking the first exclusive waiter, so this
loses the wakeup and can leave other waiters asleep indefinitely on an
unlocked folio.&lt;/p&gt;
&lt;p&gt;After finish_wait(), let a waiter woken without a lock handoff try once
more to acquire the lock. If successful, return success so the caller&amp;#39;s
eventual unlock wakes the next waiter. Otherwise, the current lock owner
will do so.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: clarify and simplify comment + description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99731</guid>
    </item>
    <item>
      <title>GHSA-26f4-r329-2c97</title>
      <link>https://db.gcve.eu/vuln/ghsa-26f4-r329-2c97</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/filemap: don&amp;#39;t lose a folio lock wakeup to a signal&lt;/p&gt;
&lt;p&gt;An exclusive waiter in folio_wait_bit_common() can leave the wait loop
because of a fatal signal, then be woken by folio_unlock() before
finish_wait(). If the waker did not hand over the lock, the waiter returns
-EINTR without trying to acquire it.&lt;/p&gt;
&lt;p&gt;folio_wake_bit() stops after waking the first exclusive waiter, so this
loses the wakeup and can leave other waiters asleep indefinitely on an
unlocked folio.&lt;/p&gt;
&lt;p&gt;After finish_wait(), let a waiter woken without a lock handoff try once
more to acquire the lock. If successful, return success so the caller&amp;#39;s
eventual unlock wakes the next waiter. Otherwise, the current lock owner
will do so.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: clarify and simplify comment + description ]&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;mm/filemap: don&amp;#39;t lose a folio lock wakeup to a signal&lt;/p&gt;
&lt;p&gt;An exclusive waiter in folio_wait_bit_common() can leave the wait loop
because of a fatal signal, then be woken by folio_unlock() before
finish_wait(). If the waker did not hand over the lock, the waiter returns
-EINTR without trying to acquire it.&lt;/p&gt;
&lt;p&gt;folio_wake_bit() stops after waking the first exclusive waiter, so this
loses the wakeup and can leave other waiters asleep indefinitely on an
unlocked folio.&lt;/p&gt;
&lt;p&gt;After finish_wait(), let a waiter woken without a lock handoff try once
more to acquire the lock. If successful, return success so the caller&amp;#39;s
eventual unlock wakes the next waiter. Otherwise, the current lock owner
will do so.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Josef Bacik in private.&lt;/p&gt;
&lt;p&gt;[ david: clarify and simplify comment + description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-26f4-r329-2c97</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</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-4695</guid>
    </item>
  </channel>
</rss>
