CVE-2026-64558

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-29. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 29, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

s390/pkey: Check length in pkey_pckmo handler implementation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/614aa0491c7a190556c2345dddee0b6f5ed90989
generic

s390/pkey: Check length in pkey_pckmo handler implementation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/433e5e70cdc1edf382d28d08a885b22e2b98b7da
generic

s390/pkey: Check length in pkey_pckmo handler implementation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ac287e2af9a9112fe271427ef45eceb26bce8b4
generic

s390/pkey: Check length in pkey_pckmo handler implementation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02028a24e26d85262ab9c8fc4344e1f3503007fc

Vendor Advisories for CVE-2026-64558(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)7.1.5-1

Data Freshness Timeline

(refreshed 20× in last 7d / 102× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 114 total refreshes for this CVE.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 23:17 UTCEG score recompute
  3. 2026-08-29 23:17 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 23:52 UTCEG score recompute
  6. 2026-08-27 23:52 UTCGHSA enrichment
  7. 2026-08-27 11:46 UTCGHSA enrichment
  8. 2026-08-26 23:40 UTCEG score recompute
  9. 2026-08-26 23:40 UTCGHSA enrichment
  10. 2026-08-26 14:47 UTCEPSS rescore
  11. 2026-08-26 11:34 UTCGHSA enrichment
  12. 2026-08-25 23:27 UTCGHSA enrichment
  13. 2026-08-25 10:49 UTCGHSA enrichment
  14. 2026-08-24 22:43 UTCEG score recompute
  15. 2026-08-24 22:43 UTCGHSA enrichment
  16. 2026-08-24 10:37 UTCEG score recompute
  17. 2026-08-24 10:36 UTCGHSA enrichment
  18. 2026-08-23 22:29 UTCGHSA enrichment
  19. 2026-08-23 10:24 UTCEG score recompute
  20. 2026-08-23 10:24 UTCGHSA enrichment
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 22:13 UTCGHSA enrichment
  23. 2026-08-22 10:07 UTCEG score recompute
  24. 2026-08-22 10:07 UTCGHSA enrichment
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 22:01 UTCGHSA enrichment
  2. 2026-08-21 09:54 UTCEG score recompute
  3. 2026-08-21 09:54 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 21:48 UTCGHSA enrichment
  6. 2026-08-20 09:43 UTCGHSA enrichment
  7. 2026-08-19 21:37 UTCEG score recompute
  8. 2026-08-19 21:37 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 09:00 UTCGHSA enrichment
  11. 2026-08-18 20:52 UTCEG score recompute
  12. 2026-08-18 20:51 UTCGHSA enrichment
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-18 08:46 UTCGHSA enrichment
  15. 2026-08-17 19:54 UTCGHSA enrichment
  16. 2026-08-17 05:42 UTCEG score recompute
  17. 2026-08-17 05:42 UTCGHSA enrichment
  18. 2026-08-17 05:14 UTCGHSA enrichment
  19. 2026-08-17 03:19 UTCGHSA enrichment
  20. 2026-08-16 15:13 UTCEG score recompute
  21. 2026-08-16 15:13 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 03:07 UTCEG score recompute
  24. 2026-08-16 03:07 UTCGHSA enrichment
  25. 2026-08-15 15:02 UTCGHSA enrichment
  26. 2026-08-15 02:56 UTCEG score recompute
  27. 2026-08-15 02:56 UTCGHSA enrichment
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 14:50 UTCGHSA enrichment
  30. 2026-08-14 02:44 UTCEG score recompute
  31. 2026-08-14 02:44 UTCGHSA enrichment
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-13 14:38 UTCGHSA enrichment
  34. 2026-08-13 02:33 UTCGHSA enrichment
  35. 2026-08-12 14:27 UTCEG score recompute
  36. 2026-08-12 14:27 UTCGHSA enrichment
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-12 02:22 UTCGHSA enrichment
  39. 2026-08-11 14:16 UTCGHSA enrichment
  40. 2026-08-11 02:10 UTCEG score recompute
  41. 2026-08-11 02:10 UTCGHSA enrichment
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-10 14:05 UTCGHSA enrichment
  44. 2026-08-10 01:59 UTCGHSA enrichment
  45. 2026-08-09 13:53 UTCGHSA enrichment
  46. 2026-08-09 01:48 UTCEG score recompute
  47. 2026-08-09 01:48 UTCGHSA enrichment
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 13:43 UTCGHSA enrichment
  50. 2026-08-08 01:37 UTCEG score recompute
  51. 2026-08-08 01:37 UTCGHSA enrichment
  52. 2026-08-07 13:31 UTCGHSA enrichment
  53. 2026-08-07 01:26 UTCEG score recompute
  54. 2026-08-07 01:26 UTCGHSA enrichment
  55. 2026-08-06 13:47 UTCEPSS rescore
  56. 2026-08-06 13:21 UTCGHSA enrichment
  57. 2026-08-06 01:15 UTCGHSA enrichment
  58. 2026-08-05 13:10 UTCEG score recompute
  59. 2026-08-05 13:10 UTCGHSA enrichment
  60. 2026-08-05 07:56 UTCGHSA enrichment
  61. 2026-08-04 19:48 UTCEG score recompute
  62. 2026-08-04 19:48 UTCGHSA enrichment
  63. 2026-08-04 15:10 UTCEPSS rescore
  64. 2026-08-04 07:42 UTCGHSA enrichment
  65. 2026-08-03 19:36 UTCEG score recompute
  66. 2026-08-03 19:36 UTCGHSA enrichment
  67. 2026-08-03 10:36 UTCEPSS rescore
  68. 2026-08-03 07:30 UTCGHSA enrichment
  69. 2026-08-02 19:23 UTCGHSA enrichment
  70. 2026-08-02 07:18 UTCEG score recompute
  71. 2026-08-02 07:18 UTCGHSA enrichment
  72. 2026-08-02 02:27 UTCEPSS rescore
  73. 2026-08-01 19:12 UTCGHSA enrichment
  74. 2026-08-01 07:06 UTCEG score recompute
  75. 2026-08-01 07:06 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64558?
CVE-2026-64558 is a high vulnerability published on July 29, 2026. 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 keytoprotkey() handler function. The handler function fails, if the generated…
When was CVE-2026-64558 disclosed?
CVE-2026-64558 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64558 actively exploited?
CVE-2026-64558 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64558?
CVE-2026-64558 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64558?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64558, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64558

Explore →

Is Your Infrastructure Affected by CVE-2026-64558?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.