<?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 21:28:04 +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-98537</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98537</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;workqueue: Fix NULL current_pwq deref in flush dependency check&lt;/p&gt;
&lt;p&gt;check_flush_dependency() uses current_wq_worker() to determine whether
the caller is a workqueue worker and then dereferences worker-&amp;gt;current_pwq
to test whether the current workqueue is WQ_MEM_RECLAIM.&lt;/p&gt;
&lt;p&gt;current_wq_worker() only means that %current has PF_WQ_WORKER set. A
kworker can reach check_flush_dependency() while it is not executing a
work item. One such path is worker_thread() acting as the pool manager,
where create_worker() does GFP_KERNEL allocation and the allocation path
invokes the OOM notifier. In that state worker-&amp;gt;current_pwq is NULL
because current_pwq is set only by process_one_work() and cleared again
after the work function returns.&lt;/p&gt;
&lt;p&gt;[  416.760634][  T375] Call trace:
[  416.760638][  T375]  check_flush_dependency+0x80/0x120 (P)
[  416.760648][  T375]  __flush_work+0x98/0x224
[  416.760657][  T375]  flush_work+0x30/0x44
[  416.760665][  T375]  ...
[  416.760710][  T375]  blocking_notifier_call_chain+0x58/0xa0
[  416.760719][  T375]  out_of_memory+0xb4/0x458
[  416.760730][  T375]  __alloc_pages_may_oom+0x11c/0x1a8
[  416.760739][  T375]  __alloc_pages_slowpath+0x314/0x46c
[  416.760746][  T375]  __alloc_frozen_pages_noprof+0x110/0x1a4
[  416.760753][  T375]  new_slab+0x12c/0x484
[  416.760759][  T375]  ___slab_alloc+0x7a8/0xc7c
[  416.760765][  T375]  __slab_alloc+0x74/0xd8
[  416.760772][  T375]  __kmalloc_cache_node_nopr…&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;workqueue: Fix NULL current_pwq deref in flush dependency check&lt;/p&gt;
&lt;p&gt;check_flush_dependency() uses current_wq_worker() to determine whether
the caller is a workqueue worker and then dereferences worker-&amp;gt;current_pwq
to test whether the current workqueue is WQ_MEM_RECLAIM.&lt;/p&gt;
&lt;p&gt;current_wq_worker() only means that %current has PF_WQ_WORKER set. A
kworker can reach check_flush_dependency() while it is not executing a
work item. One such path is worker_thread() acting as the pool manager,
where create_worker() does GFP_KERNEL allocation and the allocation path
invokes the OOM notifier. In that state worker-&amp;gt;current_pwq is NULL
because current_pwq is set only by process_one_work() and cleared again
after the work function returns.&lt;/p&gt;
&lt;p&gt;[  416.760634][  T375] Call trace:
[  416.760638][  T375]  check_flush_dependency+0x80/0x120 (P)
[  416.760648][  T375]  __flush_work+0x98/0x224
[  416.760657][  T375]  flush_work+0x30/0x44
[  416.760665][  T375]  ...
[  416.760710][  T375]  blocking_notifier_call_chain+0x58/0xa0
[  416.760719][  T375]  out_of_memory+0xb4/0x458
[  416.760730][  T375]  __alloc_pages_may_oom+0x11c/0x1a8
[  416.760739][  T375]  __alloc_pages_slowpath+0x314/0x46c
[  416.760746][  T375]  __alloc_frozen_pages_noprof+0x110/0x1a4
[  416.760753][  T375]  new_slab+0x12c/0x484
[  416.760759][  T375]  ___slab_alloc+0x7a8/0xc7c
[  416.760765][  T375]  __slab_alloc+0x74/0xd8
[  416.760772][  T375]  __kmalloc_cache_node_nopr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98537</guid>
    </item>
    <item>
      <title>GHSA-6w2x-9phq-jcjc</title>
      <link>https://db.gcve.eu/vuln/ghsa-6w2x-9phq-jcjc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;workqueue: Fix NULL current_pwq deref in flush dependency check&lt;/p&gt;
&lt;p&gt;check_flush_dependency() uses current_wq_worker() to determine whether
the caller is a workqueue worker and then dereferences worker-&amp;gt;current_pwq
to test whether the current workqueue is WQ_MEM_RECLAIM.&lt;/p&gt;
&lt;p&gt;current_wq_worker() only means that %current has PF_WQ_WORKER set. A
kworker can reach check_flush_dependency() while it is not executing a
work item. One such path is worker_thread() acting as the pool manager,
where create_worker() does GFP_KERNEL allocation and the allocation path
invokes the OOM notifier. In that state worker-&amp;gt;current_pwq is NULL
because current_pwq is set only by process_one_work() and cleared again
after the work function returns.&lt;/p&gt;
&lt;p&gt;[  416.760634][  T375] Call trace:
[  416.760638][  T375]  check_flush_dependency+0x80/0x120 (P)
[  416.760648][  T375]  __flush_work+0x98/0x224
[  416.760657][  T375]  flush_work+0x30/0x44
[  416.760665][  T375]  ...
[  416.760710][  T375]  blocking_notifier_call_chain+0x58/0xa0
[  416.760719][  T375]  out_of_memory+0xb4/0x458
[  416.760730][  T375]  __alloc_pages_may_oom+0x11c/0x1a8
[  416.760739][  T375]  __alloc_pages_slowpath+0x314/0x46c
[  416.760746][  T375]  __alloc_frozen_pages_noprof+0x110/0x1a4
[  416.760753][  T375]  new_slab+0x12c/0x484
[  416.760759][  T375]  ___slab_alloc+0x7a8/0xc7c
[  416.760765][  T375]  __slab_alloc+0x74/0xd8
[  416.760772][  T375]  __kmalloc_cache_node_nopr…&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;workqueue: Fix NULL current_pwq deref in flush dependency check&lt;/p&gt;
&lt;p&gt;check_flush_dependency() uses current_wq_worker() to determine whether
the caller is a workqueue worker and then dereferences worker-&amp;gt;current_pwq
to test whether the current workqueue is WQ_MEM_RECLAIM.&lt;/p&gt;
&lt;p&gt;current_wq_worker() only means that %current has PF_WQ_WORKER set. A
kworker can reach check_flush_dependency() while it is not executing a
work item. One such path is worker_thread() acting as the pool manager,
where create_worker() does GFP_KERNEL allocation and the allocation path
invokes the OOM notifier. In that state worker-&amp;gt;current_pwq is NULL
because current_pwq is set only by process_one_work() and cleared again
after the work function returns.&lt;/p&gt;
&lt;p&gt;[  416.760634][  T375] Call trace:
[  416.760638][  T375]  check_flush_dependency+0x80/0x120 (P)
[  416.760648][  T375]  __flush_work+0x98/0x224
[  416.760657][  T375]  flush_work+0x30/0x44
[  416.760665][  T375]  ...
[  416.760710][  T375]  blocking_notifier_call_chain+0x58/0xa0
[  416.760719][  T375]  out_of_memory+0xb4/0x458
[  416.760730][  T375]  __alloc_pages_may_oom+0x11c/0x1a8
[  416.760739][  T375]  __alloc_pages_slowpath+0x314/0x46c
[  416.760746][  T375]  __alloc_frozen_pages_noprof+0x110/0x1a4
[  416.760753][  T375]  new_slab+0x12c/0x484
[  416.760759][  T375]  ___slab_alloc+0x7a8/0xc7c
[  416.760765][  T375]  __slab_alloc+0x74/0xd8
[  416.760772][  T375]  __kmalloc_cache_node_nopr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-6w2x-9phq-jcjc</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98537 — workqueue: Fix NULL current_pwq deref in flush dependency check</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98537</link>
      <description>msrc_CVE-2026-98537</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98537</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98537</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98537</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in flush dependency check check_flush_dependency() uses current_wq_worker() to determine whether the caller is a workqueue worker and then dereferences worker-&amp;gt;current_pwq to test whether the current workqueue is WQ_MEM_RECLAIM. current_wq_worker() only means that %current has PF_WQ_WORKER set. A kworker can reach check_flush_dependency() while it is not executing a work item. One such path is worker_thread() acting as the pool manager, where create_worker() does GFP_KERNEL allocation and the allocation path invokes the OOM notifier. In that state worker-&amp;gt;current_pwq is NULL because current_pwq is set only by process_one_work() and cleared again after the work function returns. [  416.760634][  T375] Call trace: [  416.760638][  T375]  check_flush_dependency+0x80/0x120 (P) [  416.760648][  T375]  __flush_work+0x98/0x224 [  416.760657][  T375]  flush_work+0x30/0x44 [  416.760665][  T375]  ... [  416.760710][  T375]  blocking_notifier_call_chain+0x58/0xa0 [  416.760719][  T375]  out_of_memory+0xb4/0x458 [  416.760730][  T375]  __alloc_pages_may_oom+0x11c/0x1a8 [  416.760739][  T375]  __alloc_pages_slowpath+0x314/0x46c [  416.760746][  T375]  __alloc_frozen_pages_noprof+0x110/0x1a4 [  416.760753][  T375]  new_slab+0x12c/0x484 [  416.760759][  T375]  ___slab_alloc+0x7a8/0xc7c [  416.760765][  T375]  __slab_alloc+0x74/0xd8 [  416.760772][  T375]  __kmalloc_cache_node_noprof+0…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in flush dependency check check_flush_dependency() uses current_wq_worker() to determine whether the caller is a workqueue worker and then dereferences worker-&amp;gt;current_pwq to test whether the current workqueue is WQ_MEM_RECLAIM. current_wq_worker() only means that %current has PF_WQ_WORKER set. A kworker can reach check_flush_dependency() while it is not executing a work item. One such path is worker_thread() acting as the pool manager, where create_worker() does GFP_KERNEL allocation and the allocation path invokes the OOM notifier. In that state worker-&amp;gt;current_pwq is NULL because current_pwq is set only by process_one_work() and cleared again after the work function returns. [  416.760634][  T375] Call trace: [  416.760638][  T375]  check_flush_dependency+0x80/0x120 (P) [  416.760648][  T375]  __flush_work+0x98/0x224 [  416.760657][  T375]  flush_work+0x30/0x44 [  416.760665][  T375]  ... [  416.760710][  T375]  blocking_notifier_call_chain+0x58/0xa0 [  416.760719][  T375]  out_of_memory+0xb4/0x458 [  416.760730][  T375]  __alloc_pages_may_oom+0x11c/0x1a8 [  416.760739][  T375]  __alloc_pages_slowpath+0x314/0x46c [  416.760746][  T375]  __alloc_frozen_pages_noprof+0x110/0x1a4 [  416.760753][  T375]  new_slab+0x12c/0x484 [  416.760759][  T375]  ___slab_alloc+0x7a8/0xc7c [  416.760765][  T375]  __slab_alloc+0x74/0xd8 [  416.760772][  T375]  __kmalloc_cache_node_noprof+0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98537</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>
