CVE-2026-99245 json
KEYS: Fix key_reject_and_link() race with keyring restriction
published 2026-11-03 5 d ago modified 2026-11-03 5 d ago also EUVD-2026-115775
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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().
Patch / fix
- Linux Linux 5.10.273, 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, 7.3.1, 7.4-rc1
- linux Debian 13 6.12.115-1
- linux Debian 14 7.2.14-1
debian advisories DEBIAN-CVE-2026-99245
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-112595
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/c7956ec99ad0e173720d95de9fa788bb077809f2 commit
- git.kernel.org/stable/c/2c3d907dd15f4e30d4c35b9f7a7a5078de6a1b1f commit
- git.kernel.org/stable/c/72f367417a6aee56821d0b0114cfd2b080008b63 commit
- git.kernel.org/stable/c/19dfc37c9deefa69dc805d01d35d1f2fd7902e33 commit
- git.kernel.org/stable/c/5787887eba0f0979a8c86d03a8e891395d5c24ad commit
- git.kernel.org/stable/c/01835d3a3709be508ae5209f806640336c48e395 commit
- git.kernel.org/stable/c/6fc0c818b1cac66003e937c8a0d3bfb23fd3f130 commit
- git.kernel.org/stable/c/23a9163cc40b4996ba1e20533b1210a1a0bee416 commit
- git.kernel.org/stable/c/0b157166e612b70f98a332b6c7be7eac6f8e9593 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99245 updated cvss 3.6
kernel: kernel: Keyring restriction bypass via race condition in key_reject_and_link()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9, openshift/ose-rhel-coreos-10affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/c7956ec99ad0e173720d95de9fa788bb077809f2
- git.kernel.org /stable/c/2c3d907dd15f4e30d4c35b9f7a7a5078de6a1b1f
- git.kernel.org /stable/c/72f367417a6aee56821d0b0114cfd2b080008b63
- git.kernel.org /stable/c/19dfc37c9deefa69dc805d01d35d1f2fd7902e33
- git.kernel.org /stable/c/5787887eba0f0979a8c86d03a8e891395d5c24ad
- git.kernel.org /stable/c/01835d3a3709be508ae5209f806640336c48e395
- git.kernel.org /stable/c/6fc0c818b1cac66003e937c8a0d3bfb23fd3f130
- git.kernel.org /stable/c/23a9163cc40b4996ba1e20533b1210a1a0bee416
- git.kernel.org /stable/c/0b157166e612b70f98a332b6c7be7eac6f8e9593
Sources
- CVE List CVE-2026-99245
- NVD CVE-2026-99245
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.