CVE-2026-31699

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 CSR to userspace if PSP command failed

When retrieving the PEK CSR, don't attempt to copy the blob 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 ffff898144612e20 by task syz.9.219/21405

CPU: 14 UID: 0 PID: 21405 Comm: syz.9.219 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 12.62.0-0 11/19/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_pek_csr+0x31f/0x590 ../drivers/crypto/ccp/sev-dev.c:1872 sev_ioctl+0x3a4/0x490 ../drivers/crypto/ccp/sev-dev.c:2562 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 CSR to userspace if PSP command failed - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

https://git.kernel.org/stable/c/607ba280f2adb5092cf5386c3935afac2ca0031a
generic

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

https://git.kernel.org/stable/c/59e9ae81f8670ccc780bc75f45a355736f640ec9
generic

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

https://git.kernel.org/stable/c/3b4fd8f15765d9a3105b834dba8a05d025e5e16e
generic

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

https://git.kernel.org/stable/c/111dcc6d0f016076745824a787d25609d0022f4c

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31699?
CVE-2026-31699 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 CSR to userspace if PSP command failed When retrieving the PEK CSR, don't attempt to copy the blob to userspace if the firmware command failed. If the failure was due to an invalid length, i.e.…
When was CVE-2026-31699 disclosed?
CVE-2026-31699 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-31699 actively exploited?
CVE-2026-31699 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-31699?
CVE-2026-31699 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31699, 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-31699

Explore →

Is Your Infrastructure Affected by CVE-2026-31699?

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

Start Free Scan →Browse All CVEs