CVE-2026-98662: Linux kernel · iio: light: gp2ap020a00f: drain irq_work after free_irq
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cc71400bc965c0d3894a38ead3d71243400c2d5e : patch Linux kernel soon.
Data as of 26 Oct 2026, 20:24 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in cc71400bc965c0d3894a38ead3d71243400c2d5e, a1769877ff52a4f1bfb9ca535d1b5113808bd602, a36814b9fe00970116d30c3143d81e7425c4d334 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in specific commits identified by their hashes. Users should update to a Linux kernel version that includes these fixes to remediate the vulnerability. No additional mitigation steps are required beyond applying the official patch.
Description
A use-after-free vulnerability exists in the Linux kernel driver for the gp2ap020a00f light sensor. The issue arises because the irq_work queued by the threaded IRQ handler is not flushed by free_irq(), allowing work to run after the device has been freed. This can lead to a use-after-free condition when iio_trigger_poll() is called on a freed trigger. The flaw has been fixed by adding irq_work_sync() calls after free_irq() in the remove and probe error paths.
References
- git.kernel.org/stable/c/85c20d1cf3f01a506605a16c2f9ce23b9c8b114f (opens in a new tab)
- git.kernel.org/stable/c/a36814b9fe00970116d30c3143d81e7425c4d334 (opens in a new tab)
- git.kernel.org/stable/c/cc71400bc965c0d3894a38ead3d71243400c2d5e (opens in a new tab)
- git.kernel.org/stable/c/a1769877ff52a4f1bfb9ca535d1b5113808bd602 (opens in a new tab)
- git.kernel.org/stable/c/63213927b141085b6c8719b8037dab3074b7e0fe (opens in a new tab)