<?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 20:51:57 +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-98662</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98662</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: light: gp2ap020a00f: drain irq_work after free_irq&lt;/p&gt;
&lt;p&gt;The threaded IRQ handler queues data-&amp;gt;work through irq_work_queue() so
the trigger is polled from a per-CPU context.  free_irq() does not flush
an irq_work the handler already queued, so after gp2ap020a00f_remove()
returns that work may still run and call iio_trigger_poll() on data-&amp;gt;trig,
which the devm cleanup has already freed, causing a use-after-free.&lt;/p&gt;
&lt;p&gt;Add irq_work_sync(&amp;amp;data-&amp;gt;work) after free_irq() in remove() and in the
probe error path, mirroring commit 78601726d4a5 (&amp;#34;iio: trigger: sysfs:
fix use-after-free on remove&amp;#34;).&lt;/p&gt;
&lt;p&gt;Found by an in-house static analysis tool, confirmed by manual review.&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;iio: light: gp2ap020a00f: drain irq_work after free_irq&lt;/p&gt;
&lt;p&gt;The threaded IRQ handler queues data-&amp;gt;work through irq_work_queue() so
the trigger is polled from a per-CPU context.  free_irq() does not flush
an irq_work the handler already queued, so after gp2ap020a00f_remove()
returns that work may still run and call iio_trigger_poll() on data-&amp;gt;trig,
which the devm cleanup has already freed, causing a use-after-free.&lt;/p&gt;
&lt;p&gt;Add irq_work_sync(&amp;amp;data-&amp;gt;work) after free_irq() in remove() and in the
probe error path, mirroring commit 78601726d4a5 (&amp;#34;iio: trigger: sysfs:
fix use-after-free on remove&amp;#34;).&lt;/p&gt;
&lt;p&gt;Found by an in-house static analysis tool, confirmed by manual review.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98662</guid>
    </item>
    <item>
      <title>GHSA-5vf6-9cv6-xwcm</title>
      <link>https://db.gcve.eu/vuln/ghsa-5vf6-9cv6-xwcm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: light: gp2ap020a00f: drain irq_work after free_irq&lt;/p&gt;
&lt;p&gt;The threaded IRQ handler queues data-&amp;gt;work through irq_work_queue() so
the trigger is polled from a per-CPU context.  free_irq() does not flush
an irq_work the handler already queued, so after gp2ap020a00f_remove()
returns that work may still run and call iio_trigger_poll() on data-&amp;gt;trig,
which the devm cleanup has already freed, causing a use-after-free.&lt;/p&gt;
&lt;p&gt;Add irq_work_sync(&amp;amp;data-&amp;gt;work) after free_irq() in remove() and in the
probe error path, mirroring commit 78601726d4a5 (&amp;#34;iio: trigger: sysfs:
fix use-after-free on remove&amp;#34;).&lt;/p&gt;
&lt;p&gt;Found by an in-house static analysis tool, confirmed by manual review.&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;iio: light: gp2ap020a00f: drain irq_work after free_irq&lt;/p&gt;
&lt;p&gt;The threaded IRQ handler queues data-&amp;gt;work through irq_work_queue() so
the trigger is polled from a per-CPU context.  free_irq() does not flush
an irq_work the handler already queued, so after gp2ap020a00f_remove()
returns that work may still run and call iio_trigger_poll() on data-&amp;gt;trig,
which the devm cleanup has already freed, causing a use-after-free.&lt;/p&gt;
&lt;p&gt;Add irq_work_sync(&amp;amp;data-&amp;gt;work) after free_irq() in remove() and in the
probe error path, mirroring commit 78601726d4a5 (&amp;#34;iio: trigger: sysfs:
fix use-after-free on remove&amp;#34;).&lt;/p&gt;
&lt;p&gt;Found by an in-house static analysis tool, confirmed by manual review.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-5vf6-9cv6-xwcm</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98662 — iio: light: gp2ap020a00f: drain irq_work after free_irq</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98662</link>
      <description>msrc_CVE-2026-98662</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98662</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98662</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98662</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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iio: light: gp2ap020a00f: drain irq_work after free_irq The threaded IRQ handler queues data-&amp;gt;work through irq_work_queue() so the trigger is polled from a per-CPU context.  free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data-&amp;gt;trig, which the devm cleanup has already freed, causing a use-after-free. Add irq_work_sync(&amp;amp;data-&amp;gt;work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 (&amp;#34;iio: trigger: sysfs: fix use-after-free on remove&amp;#34;). Found by an in-house static analysis tool, confirmed by manual review.&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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iio: light: gp2ap020a00f: drain irq_work after free_irq The threaded IRQ handler queues data-&amp;gt;work through irq_work_queue() so the trigger is polled from a per-CPU context.  free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data-&amp;gt;trig, which the devm cleanup has already freed, causing a use-after-free. Add irq_work_sync(&amp;amp;data-&amp;gt;work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 (&amp;#34;iio: trigger: sysfs: fix use-after-free on remove&amp;#34;). Found by an in-house static analysis tool, confirmed by manual review.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98662</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>
