iio: trigger: cancel reenable_work before freeing trigger
Summary
| CVE | CVE-2026-98656 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:17:18 UTC |
| Updated | 2026-10-30 13:21:16 UTC |
| 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. |
Risk And Classification
EPSS: 0.001720000 probability, percentile 0.066070000 (date 2026-11-01)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected a18aeac73c0f692ba40964f5f56e182312ae843b beec4c9e23b8293c41d3448f9807c28fc9a599d4 git | Not specified |
| CNA | Linux | Linux | affected 9020ef659885f2622cfb386cc229b6d618362895 4e790a5bd4249877bcf0c94db12ac490965f9296 git | Not specified |
| CNA | Linux | Linux | affected 9020ef659885f2622cfb386cc229b6d618362895 ac5d26a46c90ff61fd574eff4e8f0d71c905828a git | Not specified |
| CNA | Linux | Linux | affected 9020ef659885f2622cfb386cc229b6d618362895 cf513df1a2c75566cdc802d9da47f62e8d6cfd18 git | Not specified |
| CNA | Linux | Linux | affected 9020ef659885f2622cfb386cc229b6d618362895 e64703280ce7a23a43c27efebeb7da457c88bf5c git | Not specified |
| CNA | Linux | Linux | affected 9020ef659885f2622cfb386cc229b6d618362895 882d0011c59ff8ac15188ec9ce071399ecfa10ad git | Not specified |
| CNA | Linux | Linux | affected 9020ef659885f2622cfb386cc229b6d618362895 2a57b9246cecd5dd797a42eb310d6c8816f26d9e git | Not specified |
| CNA | Linux | Linux | affected 2c5c948451d57596640b20887b06b523d376eb24 git | Not specified |
| CNA | Linux | Linux | affected 5.15.17 5.15.224 semver | Not specified |
| CNA | Linux | Linux | affected 5.16.3 5.17 semver | Not specified |
| CNA | Linux | Linux | affected 5.17 | Not specified |
| CNA | Linux | Linux | unaffected 5.17 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.224 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.191 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.113 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.56 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.10 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/4e790a5bd4249877bcf0c94db12ac490965f9296 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/882d0011c59ff8ac15188ec9ce071399ecfa10ad | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ac5d26a46c90ff61fd574eff4e8f0d71c905828a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e64703280ce7a23a43c27efebeb7da457c88bf5c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/beec4c9e23b8293c41d3448f9807c28fc9a599d4 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/cf513df1a2c75566cdc802d9da47f62e8d6cfd18 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2a57b9246cecd5dd797a42eb310d6c8816f26d9e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.