# CVE-2026-97590: s390/crypto: Fix missing scrub of temp buffers with PAES algorithm

> An attacker with local access could potentially read sensitive cryptographic data from unscrubbed temporary buffers in the s390 PAES implementation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-97590, DEBIAN-CVE-2026-97590, GHSA-9wm4-m683-cr29, UBUNTU-CVE-2026-97590

## What is CVE-2026-97590?

CVE-2026-97590 is a vulnerability in Linux, published on 25 Sep 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

s390/crypto: Fix missing scrub of temp buffers with PAES algorithm

In function ctr_paes_do_crypt() there is a buffer used to process
remaining bytes < AES_BLOCK_SIZE. This buffer was not scrubbed and
thus could lead to expose of unwanted data. Rework the code to
explicitly scrub the buffer at the end of the function to avoid
exposure of maybe sensitive data.

In function __xts_2keys_prep_param() change the existing scrub to
clean the whole param block instead of just the key field.

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


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

Apply the vendor's patch.

## Is CVE-2026-97590 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97590 is a vulnerability in Linux, published on 25 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-97590 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-97590/ (Markdown: https://insights.sbomify.com/CVE-2026-97590/index.md)
```

## Sources

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

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