Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-31697

7.1 · HIGH

In the Linux kernel, the following vulnerability has been resolved: crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed When retrieving the ID for the CPU, don't attempt to c…

Published May 1, 2026CWE-787EPSS 0.17%

Overview

CVE-2026-31697 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.1 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

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

When retrieving the ID for the CPU, don't attempt to copy the ID 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 64 at addr ffff8881867f5960 by task syz.0.906/24388

CPU: 130 UID: 0 PID: 24388 Comm: syz.0.906 Tainted: G U O 7.0.0-smp-DEV #28 PREEMPTLAZY

Tainted: [U]=USER, [O]=OOT_MODULE

Hardware name: Google, Inc. Arcadia

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/06f06d88c05ce176c61fff8c72c372847b0dd2b5Refgit.kernel.org/stable/c/09427bcb1715fb20a80b6acd5156dbf15ab5c363Refgit.kernel.org/stable/c/0f1f2f9894893dc8a28af1b9e9dbc0abf453eb52Refgit.kernel.org/stable/c/1fbac0429a42adec830491757a2b53956dd797eaRefgit.kernel.org/stable/c/2937f17bbeefb8e7608ff1f78cffbeb3d0281e5eRefgit.kernel.org/stable/c/4f685dbfa87c546e51d9dc6cab379d20f275e114Refgit.kernel.org/stable/c/99bae2e3c3f9ba8f854c938ed2c811b6a63b28e4Refgit.kernel.org/stable/c/a21ae9f8769e5f75433bb0a85ac3868b2100ef5b

How CyberStrike helps

Frequently asked questions

What is CVE-2026-31697?

CVE-2026-31697 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.1 (HIGH).

How severe is CVE-2026-31697?

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31697?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31697?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31697 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999