# CVE-2026-98670: iio: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind

> A race condition in the Xilinx XADC driver allows a use-after-free during device unbind, potentially leading to system crashes or code execution.

- **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-109361, BELL-CVE-2026-98670, DEBIAN-CVE-2026-98670, GHSA-pfxr-v75f-fxq3, UBUNTU-CVE-2026-98670

## What is CVE-2026-98670?

CVE-2026-98670 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: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind

The ZYNQ XADC alarm IRQ handler queues zynq_unmask_work via
schedule_delayed_work(); that work is cleared by a devm callback.
Register the devm callback before devm_request_irq() so the devres LIFO
teardown frees the IRQ first, ensuring the handler can no longer queue
work by the time the workqueue is cleared. Otherwise the handler could
re-arm the work and run it after the xadc structure has been freed.

This issue was found by an in-house static analysis tool.

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


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

Apply the vendor's patch.

## Is CVE-2026-98670 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98670 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-98670 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-98670/ (Markdown: https://insights.sbomify.com/CVE-2026-98670/index.md)
```

## Sources

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

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