# s390/pkey: Check length in pkey_pckmo handler implementation

CVE record · `CVE-2026-64558`

- **Identifiers:** `CVE-2026-64558`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-122](https://cwe.mitre.org/data/definitions/122.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 29 Jul 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 29 Jul 2026, 16:31 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: `8fcc231ce3bea12b78bb94b280cdc03cff342435 to before 02028a24e26d85262ab9c8fc4344e1f3503007fc` (git)
  - affected: `8fcc231ce3bea12b78bb94b280cdc03cff342435 to before 433e5e70cdc1edf382d28d08a885b22e2b98b7da` (git)
  - affected: `8fcc231ce3bea12b78bb94b280cdc03cff342435 to before 614aa0491c7a190556c2345dddee0b6f5ed90989` (git)
  - affected: `8fcc231ce3bea12b78bb94b280cdc03cff342435 to before 1ac287e2af9a9112fe271427ef45eceb26bce8b4` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.12`
  - unaffected: `before 6.12` (semver)
  - unaffected: `6.12.97 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.40 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.5 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 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

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 29 Jul 2026, 17:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-64558)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/02028a24e26d85262ab9c8fc4344e1f3503007fc>
- <https://git.kernel.org/stable/c/433e5e70cdc1edf382d28d08a885b22e2b98b7da>
- <https://git.kernel.org/stable/c/614aa0491c7a190556c2345dddee0b6f5ed90989>
- <https://git.kernel.org/stable/c/1ac287e2af9a9112fe271427ef45eceb26bce8b4>

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-64558>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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