<?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:02 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99058</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99058</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 chained work check&lt;/p&gt;
&lt;p&gt;current_wq_worker() only tells us that %current is a kworker. It does
not guarantee that the worker is currently executing a work item, as
worker-&amp;gt;current_pwq is populated only while process_one_work() is running
the work function.&lt;/p&gt;
&lt;p&gt;is_chained_work() can be reached while queueing on a draining or
destroying workqueue. If a kworker outside work-item execution reaches
that path, current_wq_worker() returns a worker but worker-&amp;gt;current_pwq is
NULL, and the chained-work test can fault before it emits the intended
warning.&lt;/p&gt;
&lt;p&gt;Guard the chained-work test with worker-&amp;gt;current_pwq. A kworker without
current_pwq is not executing work on the target workqueue, so the helper
should return false and let the draining/destroying warning fire.&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 chained work check&lt;/p&gt;
&lt;p&gt;current_wq_worker() only tells us that %current is a kworker. It does
not guarantee that the worker is currently executing a work item, as
worker-&amp;gt;current_pwq is populated only while process_one_work() is running
the work function.&lt;/p&gt;
&lt;p&gt;is_chained_work() can be reached while queueing on a draining or
destroying workqueue. If a kworker outside work-item execution reaches
that path, current_wq_worker() returns a worker but worker-&amp;gt;current_pwq is
NULL, and the chained-work test can fault before it emits the intended
warning.&lt;/p&gt;
&lt;p&gt;Guard the chained-work test with worker-&amp;gt;current_pwq. A kworker without
current_pwq is not executing work on the target workqueue, so the helper
should return false and let the draining/destroying warning fire.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99058</guid>
    </item>
    <item>
      <title>GHSA-vhm2-x82m-jxjm</title>
      <link>https://db.gcve.eu/vuln/ghsa-vhm2-x82m-jxjm</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 chained work check&lt;/p&gt;
&lt;p&gt;current_wq_worker() only tells us that %current is a kworker. It does
not guarantee that the worker is currently executing a work item, as
worker-&amp;gt;current_pwq is populated only while process_one_work() is running
the work function.&lt;/p&gt;
&lt;p&gt;is_chained_work() can be reached while queueing on a draining or
destroying workqueue. If a kworker outside work-item execution reaches
that path, current_wq_worker() returns a worker but worker-&amp;gt;current_pwq is
NULL, and the chained-work test can fault before it emits the intended
warning.&lt;/p&gt;
&lt;p&gt;Guard the chained-work test with worker-&amp;gt;current_pwq. A kworker without
current_pwq is not executing work on the target workqueue, so the helper
should return false and let the draining/destroying warning fire.&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 chained work check&lt;/p&gt;
&lt;p&gt;current_wq_worker() only tells us that %current is a kworker. It does
not guarantee that the worker is currently executing a work item, as
worker-&amp;gt;current_pwq is populated only while process_one_work() is running
the work function.&lt;/p&gt;
&lt;p&gt;is_chained_work() can be reached while queueing on a draining or
destroying workqueue. If a kworker outside work-item execution reaches
that path, current_wq_worker() returns a worker but worker-&amp;gt;current_pwq is
NULL, and the chained-work test can fault before it emits the intended
warning.&lt;/p&gt;
&lt;p&gt;Guard the chained-work test with worker-&amp;gt;current_pwq. A kworker without
current_pwq is not executing work on the target workqueue, so the helper
should return false and let the draining/destroying warning fire.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-vhm2-x82m-jxjm</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99058 — workqueue: Fix NULL current_pwq deref in chained work check</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99058</link>
      <description>msrc_CVE-2026-99058</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99058</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99058</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99058</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 257 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in chained work check current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker-&amp;gt;current_pwq is populated only while process_one_work() is running the work function. is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker-&amp;gt;current_pwq is NULL, and the chained-work test can fault before it emits the intended warning. Guard the chained-work test with worker-&amp;gt;current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 257 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in chained work check current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker-&amp;gt;current_pwq is populated only while process_one_work() is running the work function. is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker-&amp;gt;current_pwq is NULL, and the chained-work test can fault before it emits the intended warning. Guard the chained-work test with worker-&amp;gt;current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99058</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4152</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-4152</guid>
    </item>
  </channel>
</rss>
