Live › vulnerability › CVE-2026-98871
Go to dashboardA Linux kernel bug in the AMD CCP crypto driver's SEV initialization failure path can take a mutex twice, causing a deadlock. The sources describe a hang rather than code execution or data access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Hosts running Linux kernels with the AMD CCP driver and SEV support enabled, typically AMD EPYC servers running confidential-computing workloads. Systems without AMD SEV hardware or without the ccp module loaded are unlikely to be affected; the sources do not give further detail.
No product ranges from the sources yet.
uname -r and compare against the fixed kernel builds listed by your distributionccp module loaded with lsmod | grep ccpEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
crypto: ccp - Fix possible deadlock in SEV init failure path
__sev_platform_init_handle_init_ex_path() calls rmp_mark_pages_firmware() with locked=false while the parent function of init_ex_path already acquired the sev_cmd_mutex. In the case of an RMPUPDATE failure for any page after the first, the cleanup path would invoke reclaim pages which would result in a deadlock in sev_do_cmd.
Pass locked=true to honor the lock status of the parent function.
This page as .md · .json · in your agent: get_signal("CVE-2026-98871")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.