Skip to main content
VulnerabilityPublished Updated

CVE-2026-98656: Linux kernel · iio: trigger: cancel reenable_work before freeing trigger

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in e64703280ce7a23a43c27efebeb7da457c88bf5c : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · 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 e64703280ce7a23a43c27efebeb7da457c88bf5c, cf513df1a2c75566cdc802d9da47f62e8d6cfd18, ac5d26a46c90ff61fd574eff4e8f0d71c905828a +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.15.17 <5.16
  • >=5.16.3 <5.17
Fixed in
  • e64703280ce7a23a43c27efebeb7da457c88bf5c
  • cf513df1a2c75566cdc802d9da47f62e8d6cfd18
  • ac5d26a46c90ff61fd574eff4e8f0d71c905828a
  • 882d0011c59ff8ac15188ec9ce071399ecfa10ad
  • 5.17
  • 5.16
  • 2a57b9246cecd5dd797a42eb310d6c8816f26d9e
LinuxLinuxAffected
  • =5.17
Fixed in–

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.

References

Community reviews

Loading reviews…