Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected bf29fbeaa13d3350ca71df70c705d8b883c45692 – < 6f2bb000493c3b4f5715b3103657393672aea05b
    • affected bf29fbeaa13d3350ca71df70c705d8b883c45692 – < 43fbbb9eaae5d6f45668e3c4d45508c498d6ba9c
    • affected bf29fbeaa13d3350ca71df70c705d8b883c45692 – < d029639b079b28a5334f934c848d895bef0653d1
    • affected bf29fbeaa13d3350ca71df70c705d8b883c45692 – < 85c20d1cf3f01a506605a16c2f9ce23b9c8b114f
    • affected bf29fbeaa13d3350ca71df70c705d8b883c45692 – < a36814b9fe00970116d30c3143d81e7425c4d334
    • affected bf29fbeaa13d3350ca71df70c705d8b883c45692 – < cc71400bc965c0d3894a38ead3d71243400c2d5e
    • affected bf29fbeaa13d3350ca71df70c705d8b883c45692 – < a1769877ff52a4f1bfb9ca535d1b5113808bd602
    • affected bf29fbeaa13d3350ca71df70c705d8b883c45692 – < 63213927b141085b6c8719b8037dab3074b7e0fe
  • Linux · Linux

    • affected 3.13
    • unaffected < 3.13
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98662 badge
[![CVE-2026-98662](https://cveledger.app/badge/CVE-2026-98662.svg)](https://cveledger.app/cve/CVE-2026-98662)

Record last updated .