CVE-2026-98656: Linux kernel · iio: trigger: cancel reenable_work before freeing trigger
Source GCVE Database
Not known to be exploited · fixed in e64703280ce7a23a43c27efebeb7da457c88bf5c : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
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
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– |
AI-suggested
A fix has been implemented that cancels the deferred reenable_work before freeing the trigger in the iio subsystem. Users should apply the official kernel update that includes this fix once available. Since this is a kernel-level issue, updating to the patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or kernel mailing list advisories for the current remediation status and available updates.
Description
A use-after-free vulnerability in the Linux kernel's Industrial I/O (iio) trigger subsystem was resolved by ensuring that deferred work is canceled before the trigger is freed. The issue involved a deferred reenable_work task that could access freed memory, potentially causing instability or crashes.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98656 (opens in a new tab)
- git.kernel.org/stable/c/2a57b9246cecd5dd797a42eb310d6c8816f26d9e (opens in a new tab)
- git.kernel.org/stable/c/882d0011c59ff8ac15188ec9ce071399ecfa10ad (opens in a new tab)
- git.kernel.org/stable/c/cf513df1a2c75566cdc802d9da47f62e8d6cfd18 (opens in a new tab)
- git.kernel.org/stable/c/e64703280ce7a23a43c27efebeb7da457c88bf5c (opens in a new tab)