CVE-2026-31699: crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed

Published May 1, 2026
·
Updated

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

Affected Software

8 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.134.1-2
Linux Linux kernel>=4.16<6.6.136
Linux Linux kernel>=6.7<6.12.84
Linux Linux kernel>=6.13<6.18.25
Linux Linux kernel>=6.19<7.0.2
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In the Linux kernel crypto ccp sev-dev path (sev_ioctl_do_pek_csr / SEV ioctl handling), change logic so that when the underlying PSP/firmware command fails, the driver does not attempt to copy the PEK CSR blob to userspace (avoids the slab out-of-bounds during copy_to_user/_copy_to_user).

    crypto: ccp (sev-dev) PEK CSR copying behavior = Do not attempt to copy the PEK CSR/CSR blob to userspace when the PSP/firmware command failed

Event History

May 1, 2026
CVE Published
via MITRE·01:55 PM
Data Sourced
via MITRE·01:55 PM
DescriptionSeverity
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 2, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-31699?

CVE-2026-31699 has been classified with a moderate severity level due to potential issues in the Linux kernel's handling of certain commands.

2

How do I fix CVE-2026-31699?

To fix CVE-2026-31699, you should update your Linux kernel to the latest version that addresses this vulnerability.

3

What systems are affected by CVE-2026-31699?

CVE-2026-31699 affects multiple versions of the Linux kernel, particularly between version 4.16 and certain releases of version 7.1.

4

What kind of vulnerability is CVE-2026-31699?

CVE-2026-31699 is a vulnerability related to the crypto subsystem in the Linux kernel, specifically concerning command handling failures.

5

Is there any exploit known for CVE-2026-31699?

As of now, there are no public exploits reported for CVE-2026-31699, but it is advisable to apply the necessary patches to mitigate potential risks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203