# CVE-2026-97589: s390/crypto: Fix wrong return code to engine in asynch callbacks

> Incorrect return codes in s390 crypto drivers cause double completions, potentially leading to system instability or crashes.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-97589, DEBIAN-CVE-2026-97589, GHSA-x8r8-vhc5-qmvr, UBUNTU-CVE-2026-97589

## What is CVE-2026-97589?

CVE-2026-97589 is a high-severity vulnerability in Linux, published on 25 Sep 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/crypto: Fix wrong return code to engine in asynch callbacks

When crypto_finalize_hash_request() or
crypto_finalize_skcipher_request() explicitly completes a request, the
do_one_request callback must return 0 to indicate successful
handling. Returning a negative error code causes the crypto engine to
assume the driver failed to take ownership and triggers a second
completion via crypto_request_complete(), resulting in a double
completion. This pattern occurs in paes_s390.c 4 times and once in
phmac_s390.c.

Fixed in phmac_do_one_request() and all four paes do_one_request
callbacks (ecb, cbc, ctr, xts) by returning 0 after explicit
finalization instead of propagating the error code.

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


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

Apply the vendor's patch.

## Is CVE-2026-97589 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97589 is a high-severity vulnerability in Linux, published on 25 Sep 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-97589 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-97589/ (Markdown: https://insights.sbomify.com/CVE-2026-97589/index.md)
```

## Sources

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

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