# s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine

CVE record · `CVE-2026-97591`

- **Identifiers:** `CVE-2026-97591`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 25 Sept 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 25 Sept 2026, 10:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `cbbc675506cc4cd93e6f895e7c1f693156f9a95c to before 203702f0013f9b7324e8c5facb6cd6e9c0942b13` (git)
  - affected: `cbbc675506cc4cd93e6f895e7c1f693156f9a95c to before bcd7f1f1e2f2882ad206f72425255be105178151` (git)
  - affected: `cbbc675506cc4cd93e6f895e7c1f693156f9a95c to before 330148371401de474b656eaf521861f12ec1a1ce` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.17`
  - unaffected: `before 6.17` (semver)
  - unaffected: `6.18.53 to 6.18.*, inclusive` (semver)
  - unaffected: `7.2.7 to 7.2.*, inclusive` (semver)
  - unaffected: `7.3 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 9th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 25 Sept 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-97591](https://www.cve.org/CVERecord?id=CVE-2026-97591)
- [NVD: CVE-2026-97591](https://nvd.nist.gov/vuln/detail/CVE-2026-97591)

### References from the CNA

- <https://git.kernel.org/stable/c/203702f0013f9b7324e8c5facb6cd6e9c0942b13>
- <https://git.kernel.org/stable/c/bcd7f1f1e2f2882ad206f72425255be105178151>
- <https://git.kernel.org/stable/c/330148371401de474b656eaf521861f12ec1a1ce>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-97591>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-97591/>. Everything for agents: <https://agentprime.io/llms.txt>.