---
id: "CVE-2026-99245"
kind: "vulnerability"
aliases: ["CVE-2026-99245"]
title: "Linux kernel: keyring restriction race lets rejected keys link"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["kernel-keyring", "linux-kernel", "runtime"]
not_affected_if: ["unknown"]
published_at: "2026-11-03T12:17:30+00:00"
first_seen_at: "2026-11-03T12:20:38+00:00"
updated_at: "2026-11-03T12:23:02+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99245", "first_seen_at": "2026-11-03T12:20:38+00:00"}]
---

# Linux kernel: keyring restriction race lets rejected keys link

A race in the Linux kernel's key management code can let a key link into a keyring even when a restriction was meant to reject it. The sources do not state what an attacker gains beyond bypassing that keyring restriction.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-11-03T12:20:38+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99245

## From the sources

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

KEYS: Fix key_reject_and_link() race with keyring restriction

The restrict_link check in key_reject_and_link() is done before taking
the keyring semaphore, racing with a concurrent keyring_restrict()
that installs the restriction while holding the semaphore in write
mode.

Move the check to after __key_link_lock(), so it is done under the
semaphore, matching the pattern used in __key_create_or_update().

---

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