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-98656

iio: trigger: cancel reenable_work before freeing trigger

Description

In the Linux kernel, the following vulnerability has been resolved: iio: trigger: cancel reenable_work before freeing trigger iio_trigger_notify_done_atomic() defers ->reenable() into trig->reenable_work on the system workqueue, and the worker dereferences the owning trigger through container_of(). Nothing cancels this work before iio_trig_release() frees the trigger, so a worker armed by the last in-flight IRQ can outlive the free and touch freed memory. Cancel it at the top of iio_trig_release(), which every free path reaches through the device core's final put_device(). Found by an in-house static analysis tool.

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.17% · top 93% of all CVEs (11 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 a18aeac73c0f692ba40964f5f56e182312ae843b – < beec4c9e23b8293c41d3448f9807c28fc9a599d4
    • affected 9020ef659885f2622cfb386cc229b6d618362895 – < 4e790a5bd4249877bcf0c94db12ac490965f9296
    • affected 9020ef659885f2622cfb386cc229b6d618362895 – < ac5d26a46c90ff61fd574eff4e8f0d71c905828a
    • affected 9020ef659885f2622cfb386cc229b6d618362895 – < cf513df1a2c75566cdc802d9da47f62e8d6cfd18
    • affected 9020ef659885f2622cfb386cc229b6d618362895 – < e64703280ce7a23a43c27efebeb7da457c88bf5c
    • affected 9020ef659885f2622cfb386cc229b6d618362895 – < 882d0011c59ff8ac15188ec9ce071399ecfa10ad
    • affected 9020ef659885f2622cfb386cc229b6d618362895 – < 2a57b9246cecd5dd797a42eb310d6c8816f26d9e
    • affected 2c5c948451d57596640b20887b06b523d376eb24
    • affected 5.15.17 – < 5.15.224
    • affected 5.16.3 – < 5.17
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • 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

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .