CVE-2026-64558: s390/pkey: Check length in pkey_pckmo handler implementation
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 02028a24e26d85262ab9c8fc4344e1f3503007fc, 1ac287e2af9a9112fe271427ef45eceb26bce8b4, 433e5e70cdc1edf382d28d08a885b22e2b98b7da.
Low priority for now. Upgrade to Linux Linux 02028a24e26d85262ab9c8fc4344e1f3503007fc, 1ac287e2af9a9112fe271427ef45eceb26bce8b4, 433e5e70cdc1edf382d28d08a885b22e2b98b7da or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Check length in pkey_pckmo handler implementation Explicitly check the length of the target buffer in the pkey_pckmo implementation of the key_to_protkey() handler function. The handler function fails, if the generated output data exceeds the length of the provided target buffer.
- Published
- Jul 29, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-122
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.12affected
- 8fcc231ce3bea12b78bb94b280cdc03cff342435 and later · before 02028a24e26d85262ab9c8fc4344e1f3503007fcaffected · git
- 8fcc231ce3bea12b78bb94b280cdc03cff342435 and later · before 433e5e70cdc1edf382d28d08a885b22e2b98b7daaffected · git
- 8fcc231ce3bea12b78bb94b280cdc03cff342435 and later · before 614aa0491c7a190556c2345dddee0b6f5ed90989affected · git
- 8fcc231ce3bea12b78bb94b280cdc03cff342435 and later · before 1ac287e2af9a9112fe271427ef45eceb26bce8b4affected · git
- before 6.12not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.40 and later · up to and including 6.18.*not affected · semver
- 7.1.5 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-debug-devel | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-devel | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-64k-devel-matched | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debug-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debug-devel | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debug-devel-matched | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-devel | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-devel-matched | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-doc | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-rt-64k-debug-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-rt-64k-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
| Red Hat:rhel_eus:9.6::appstream | kernel-rt-debuginfo | before 0:5.14.0-570.146.1.el9_6 | 0:5.14.0-570.146.1.el9_6 |
+70
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64556Jul 29, 2026 · perf/core: Detach event groups during remove_on_exec31Monitor
- ← EarlierCVE-2026-64557Jul 29, 2026 · Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb()35Monitor
- Later →CVE-2026-64559Jul 29, 2026 · s390/pkey: Check length in PKEY_VERIFYPROTK ioctl31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02028a24e26d85262ab9c8fc4344e1f3503007fc | Vendor (CNA) |
| Linux Linux | 1ac287e2af9a9112fe271427ef45eceb26bce8b4 | Vendor (CNA) |
| Linux Linux | 433e5e70cdc1edf382d28d08a885b22e2b98b7da | Vendor (CNA) |
| Linux Linux | 614aa0491c7a190556c2345dddee0b6f5ed90989 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-570.146.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-6393910 days apartKVM: SEV: Compute the correct max length of the in-GHCB scratch area37Monitor
- CVE-2026-23178165 days apartHID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report()31Monitor
- CVE-2025-68795197 days apartethtool: Avoid overflowing userspace buffer on stats query31Monitor
- CVE-2026-645244 days apartdrm/hyperv: validate resolution_count and fix WIN8 fallback30Monitor
- CVE-2026-6829312 days apartnet/mlx5: Fix MCIA register buffer overflow on 32 dword reads28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.