---
id: "CVE-2026-98871"
kind: "vulnerability"
aliases: ["CVE-2026-98871"]
title: "Linux kernel: SEV init failure path can deadlock the AMD CCP driver"
severity: "unknown"
cvss: null
epss: 0.00209
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["amd-sev", "infrastructure", "linux-kernel", "self-hosted"]
not_affected_if: ["no-amd-sev-hardware"]
published_at: "2026-10-23T12:18:20+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:51+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98871", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-98871", "first_seen_at": "2026-10-25T12:38:51+00:00"}]
---

# Linux kernel: SEV init failure path can deadlock the AMD CCP driver

A 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, check and fix written by a model from the sources; labelled as such._

## How to check

- `uname -r` and compare against the fixed kernel builds listed by your distribution
- Check whether the host has an AMD SEV-capable CPU and the `ccp` module loaded with `lsmod | grep ccp`

## Fix

- Update the Linux kernel to a release that includes the upstream commit fixing the SEV init failure path (version unknown from the sources)

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98871
- 2026-10-25T12:38:51+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-98871

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_