# CVE-2026-98656: iio: trigger: cancel reenable_work before freeing trigger

> A use-after-free vulnerability in the Linux kernel IIO trigger subsystem allows attackers to cause denial of service or execute code via race conditions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-108942, BELL-CVE-2026-98656, DEBIAN-CVE-2026-98656, GHSA-6556-hh6q-qw3c, UBUNTU-CVE-2026-98656

## What is CVE-2026-98656?

CVE-2026-98656 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98656?


## How do I fix CVE-2026-98656?

Apply the vendor's patch.

## Is CVE-2026-98656 being exploited?

There is no known exploitation of CVE-2026-98656 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98656 and fix it if it is affected.

What it is: CVE-2026-98656 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98656 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98656/ (Markdown: https://insights.sbomify.com/CVE-2026-98656/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98656
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98656
- OSV: https://osv.dev/vulnerability/CVE-2026-98656

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98656/
Summaries are generated and may contain mistakes; the official description above is the record.