CVE-2026-31699

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.1EG
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.1Exploit: 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:

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)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 1, 2026

Last Modified

August 5, 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.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.258—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.1-1~exp1 (129 versions)7.0.3-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 73× 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 256 total refreshes for this CVE.

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

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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