# CVE-2026-72290: KVM: s390: pci: Fix GISC refcount leak on AIF enable failure

> A refcount leak in KVM s390 PCI handling allows local attackers to cause resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72290, DEBIAN-CVE-2026-72290, GHSA-w6f2-9h8p-7g45, UBUNTU-CVE-2026-72290

## What is CVE-2026-72290?

CVE-2026-72290 is a denial of service vulnerability in Linux, published on 15 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:

KVM: s390: pci: Fix GISC refcount leak on AIF enable failure

kvm_s390_gisc_register() registers the guest ISC before pinning
the guest interrupt forwarding pages and allocating the AISB bit.
If any of the later setup steps fails, the function unwinds the
pinned pages and other local state, but does not unregister the
GISC reference. Add the missing kvm_s390_gisc_unregister() to the
error unwind path.

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


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

Apply the vendor's patch.

## Is CVE-2026-72290 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72290 is a denial of service vulnerability in Linux, published on 15 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-72290 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-72290/ (Markdown: https://insights.sbomify.com/CVE-2026-72290/index.md)
```

## Sources

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

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