CVE-2026-31698

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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:

crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed

When retrieving the PDH cert, don't attempt to copy the blobs to userspace if the firmware command failed. If the failure was due to an invalid length, i.e. the userspace buffer+length was too small, copying the number of bytes _firmware_ requires will overflow the kernel-allocated buffer and leak data to userspace.

BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline] BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline] BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26 Read of size 2084 at addr ffff8885c4ab8aa0 by task syz.0.186/21033

CPU: 51 UID: 0 PID: 21033 Comm: syz.0.186 Tainted: G U O 7.0.0-smp-DEV #28 PREEMPTLAZY Tainted: [U]=USER, [O]=OOT_MODULE Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.84.12-0 11/17/2025 Call Trace: dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120 print_address_description ../mm/kasan/report.c:378 [inline] print_report+0xbc/0x260 ../mm/kasan/report.c:482 kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595 check_region_inline ../mm/kasan/generic.c:-1 [inline] kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200 instrument_copy_to_user ../include/linux/instrumented.h:129 [inline] _inline_copy_to_user ../include/linux/uaccess.h:205 [inline] _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26 copy_to_user ../include/linux/uaccess.h:236 [inline] sev_ioctl_do_pdh_export+0x3d3/0x7c0 ../drivers/crypto/ccp/sev-dev.c:2347 sev_ioctl+0x2a2/0x490 ../drivers/crypto/ccp/sev-dev.c:2568 vfs_ioctl ../fs/ioctl.c:51 [inline] __do_sys_ioctl ../fs/ioctl.c:597 [inline] __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583 do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e

WARN if the driver says the command succeeded, but the firmware error code says otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any firwmware error.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
2.6%
KEV
Not listed

Published

May 1, 2026

Last Modified

June 14, 2026

Advisory Details (5)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e76239fed3cffd6d304d8ca3ce23984fd24f57d3
generic

crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b5c14bd4da1f376f385722fe1da993f1edab6472
generic

crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78b97e43d0b3e674d9d49ae56937b11e2ba3fcaf
generic

crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50808c13452dae43a2c90b1bbbf9daa16501ce70
generic

crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/051e51aa55fd4cdc3e8283cf4476aeeb5f563274

Vendor Advisories for CVE-2026-31698(2)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 171 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31698?
CVE-2026-31698 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed When retrieving the PDH cert, don't attempt to copy the blobs to userspace if the firmware command failed. If the failure was due to an invalid length,…
When was CVE-2026-31698 disclosed?
CVE-2026-31698 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31698 actively exploited?
CVE-2026-31698 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31698?
CVE-2026-31698 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31698?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31698, 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

Explore the affected products and dependency analysis for CVE-2026-31698

Explore →

Is Your Infrastructure Affected by CVE-2026-31698?

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

Start Free Scan →Browse All CVEs