Live › vulnerability › CVE-2026-98662
Go to dashboardThe gp2ap020a00f IIO light sensor driver can run queued interrupt work after its device is removed, touching freed trigger memory. The sources do not say what an attacker gets beyond a use-after-free in the kernel.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only systems loading the gp2ap020a00f IIO light sensor driver are in scope, which means Linux machines with that sensor hardware bound to the driver. unknown whether the sources list affected kernel versions.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98662")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.