<?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-03T20:08:07.829818+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/cve-2026-98662</id>
    <title>CVE-2026-98662 — iio: light: gp2ap020a00f: drain irq_work after free_irq</title>
    <updated>2026-11-03T20:08:07.831384+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>iio: light: gp2ap020a00f: drain irq_work after free_irq</p>
<p>The threaded IRQ handler queues data-&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-&gt;trig,
which the devm cleanup has already freed, causing a use-after-free.</p>
<p>Add irq_work_sync(&amp;data-&gt;work) after free_irq() in remove() and in the
probe error path, mirroring commit 78601726d4a5 ("iio: trigger: sysfs:
fix use-after-free on remove").</p>
<p>Found by an in-house static analysis tool, confirmed by manual review.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98662"/>
  </entry>
</feed>
