From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98662: iio: light: gp2ap020a00f: drain irq_work after free_irq
Date: Sun, 18 Oct 2026 17:43:57 +0200 [thread overview]
Message-ID: <2026101855-CVE-2026-98662-23a7@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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->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->trig,
which the devm cleanup has already freed, causing a use-after-free.
Add irq_work_sync(&data->work) after free_irq() in remove() and in the
probe error path, mirroring commit 78601726d4a5 ("iio: trigger: sysfs:
fix use-after-free on remove").
Found by an in-house static analysis tool, confirmed by manual review.
The Linux kernel CVE team has assigned CVE-2026-98662 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.13 with commit bf29fbeaa13d3350ca71df70c705d8b883c45692 and fixed in 6.12.113 with commit a36814b9fe00970116d30c3143d81e7425c4d334
Issue introduced in 3.13 with commit bf29fbeaa13d3350ca71df70c705d8b883c45692 and fixed in 6.18.56 with commit cc71400bc965c0d3894a38ead3d71243400c2d5e
Issue introduced in 3.13 with commit bf29fbeaa13d3350ca71df70c705d8b883c45692 and fixed in 7.2.10 with commit a1769877ff52a4f1bfb9ca535d1b5113808bd602
Issue introduced in 3.13 with commit bf29fbeaa13d3350ca71df70c705d8b883c45692 and fixed in 7.3-rc6 with commit 63213927b141085b6c8719b8037dab3074b7e0fe
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-98662
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/iio/light/gp2ap020a00f.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/a36814b9fe00970116d30c3143d81e7425c4d334
https://git.kernel.org/stable/c/cc71400bc965c0d3894a38ead3d71243400c2d5e
https://git.kernel.org/stable/c/a1769877ff52a4f1bfb9ca535d1b5113808bd602
https://git.kernel.org/stable/c/63213927b141085b6c8719b8037dab3074b7e0fe
reply other threads:[~2026-10-18 15:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026101855-CVE-2026-98662-23a7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.