Answer in brief
CVE-2026-98656 records a Unknown severity vulnerability in iio: trigger: cancel reenable_work before freeing trigger. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9020ef659885f2622cfb386cc229b6d618362895 <cf513df1a2c75566cdc802d9da47f62e8d6cfd18 || >=9020ef659885f2622cfb386cc229b6d618362895 <e64703280ce7a23a43c27efebeb7da457c88bf5c || >=9020ef659885f2622cfb386cc229b6d618362895 <882d0011c59ff8ac15188ec9ce071399ecfa10ad || >=9020ef659885f2622cfb386cc229b6d618362895 <2a57b9246cecd5dd797a42eb310d6c8816f26d9e || a18aeac73c0f692ba40964f5f56e182312ae843b || 2c5c948451d57596640b20887b06b523d376eb24 || >=5.15.17 <5.16 || >=5.16.3 <5.17 | cf513df1a2c75566cdc802d9da47f62e8d6cfd18, e64703280ce7a23a43c27efebeb7da457c88bf5c, 882d0011c59ff8ac15188ec9ce071399ecfa10ad, 2a57b9246cecd5dd797a42eb310d6c8816f26d9e, 5.16, 5.17 |
| Linux/Linuxgeneric | 5.17 | Not reported |
| Linux/Linuxgeneric | >=9020ef659885f2622cfb386cc229b6d618362895 <ac5d26a46c90ff61fd574eff4e8f0d71c905828a || >=9020ef659885f2622cfb386cc229b6d618362895 <cf513df1a2c75566cdc802d9da47f62e8d6cfd18 || >=9020ef659885f2622cfb386cc229b6d618362895 <e64703280ce7a23a43c27efebeb7da457c88bf5c || >=9020ef659885f2622cfb386cc229b6d618362895 <882d0011c59ff8ac15188ec9ce071399ecfa10ad || >=9020ef659885f2622cfb386cc229b6d618362895 <2a57b9246cecd5dd797a42eb310d6c8816f26d9e || a18aeac73c0f692ba40964f5f56e182312ae843b || 2c5c948451d57596640b20887b06b523d376eb24 || >=5.15.17 <5.16 || >=5.16.3 <5.17 | ac5d26a46c90ff61fd574eff4e8f0d71c905828a, cf513df1a2c75566cdc802d9da47f62e8d6cfd18, e64703280ce7a23a43c27efebeb7da457c88bf5c, 882d0011c59ff8ac15188ec9ce071399ecfa10ad, 2a57b9246cecd5dd797a42eb310d6c8816f26d9e, 5.16, 5.17 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.