<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-02T21:28:04.138552+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/certfr-2026-avi-1375</id>
    <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>
    <updated>2026-11-02T21:28:04.151737+00:00</updated>
    <content>certfr-2026-avi-1375</content>
    <link href="https://db.gcve.eu/vuln/certfr-2026-avi-1375"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-98537</id>
    <title>fkie_cve-2026-98537</title>
    <updated>2026-11-02T21:28:04.151808+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>workqueue: Fix NULL current_pwq deref in flush dependency check</p>
<p>check_flush_dependency() uses current_wq_worker() to determine whether
the caller is a workqueue worker and then dereferences worker-&gt;current_pwq
to test whether the current workqueue is WQ_MEM_RECLAIM.</p>
<p>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-&gt;current_pwq is NULL
because current_pwq is set only by process_one_work() and cleared again
after the work function returns.</p>
<p>[  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…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98537"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-6w2x-9phq-jcjc</id>
    <title>GHSA-6w2x-9phq-jcjc</title>
    <updated>2026-11-02T21:28:04.151898+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>workqueue: Fix NULL current_pwq deref in flush dependency check</p>
<p>check_flush_dependency() uses current_wq_worker() to determine whether
the caller is a workqueue worker and then dereferences worker-&gt;current_pwq
to test whether the current workqueue is WQ_MEM_RECLAIM.</p>
<p>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-&gt;current_pwq is NULL
because current_pwq is set only by process_one_work() and cleared again
after the work function returns.</p>
<p>[  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…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-6w2x-9phq-jcjc"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-98537</id>
    <title>msrc_CVE-2026-98537 — workqueue: Fix NULL current_pwq deref in flush dependency check</title>
    <updated>2026-11-02T21:28:04.151950+00:00</updated>
    <content>msrc_CVE-2026-98537</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-98537"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-98537</id>
    <title>UBUNTU-CVE-2026-98537</title>
    <updated>2026-11-02T21:28:04.151984+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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-&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-&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…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-98537"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</id>
    <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-02T21:28:04.152429+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4019"/>
  </entry>
</feed>
