# CVE-2026-74690: s390/ism: Fix UAF of sba and ieq during ism_dev_exit()

> A use-after-free vulnerability in the s390 ISM driver allows attackers to execute arbitrary code or escalate privileges via race conditions during device exit.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-74690, DEBIAN-CVE-2026-74690, GHSA-f2p8-hwvr-fwmq, UBUNTU-CVE-2026-74690

## What is CVE-2026-74690?

CVE-2026-74690 is a high-severity use after free vulnerability in Linux, published on 22 Aug 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:

s390/ism: Fix UAF of sba and ieq during ism_dev_exit()

A ism interrupt handler can be active in parallel with ism_dev_exit(),
accessing freed data structures.

No new interrupts will be generated after unregister_ieq(). Drain ongoing
interrupt handlers by free_irq(), before freeing ism data structures.

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


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

Apply the vendor's patch.

## Is CVE-2026-74690 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74690 is a high-severity use after free vulnerability in Linux, published on 22 Aug 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-74690 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-74690/ (Markdown: https://insights.sbomify.com/CVE-2026-74690/index.md)
```

## Sources

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

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