# CVE-2026-98662: iio: light: gp2ap020a00f: drain irq_work after free_irq

> A use-after-free in the Linux kernel gp2ap020a00f driver allows local attackers to execute code or escalate privileges via race conditions during device removal.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-108587, BELL-CVE-2026-98662, DEBIAN-CVE-2026-98662, GHSA-5vf6-9cv6-xwcm, UBUNTU-CVE-2026-98662

## What is CVE-2026-98662?

CVE-2026-98662 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98662?


## How do I fix CVE-2026-98662?

Apply the vendor's patch.

## Is CVE-2026-98662 being exploited?

There is no known exploitation of CVE-2026-98662 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98662 and fix it if it is affected.

What it is: CVE-2026-98662 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98662 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98662/ (Markdown: https://insights.sbomify.com/CVE-2026-98662/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98662
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98662
- OSV: https://osv.dev/vulnerability/CVE-2026-98662

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98662/
Summaries are generated and may contain mistakes; the official description above is the record.