CVE-2026-99220 json
asymmetric_keys: reject trust keys without IDs
published 2026-11-02 6 d ago modified 2026-11-03 5 d ago also EUVD-2026-115262
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
asymmetric_keys: reject trust keys without IDs
The PKCS#8 parser deliberately leaves the asym_key_ids payload slot empty. key_or_keyring_common() unconditionally dereferences that slot when a PKCS#8 key is supplied to a key_or_keyring restriction. Both the plain and :chain forms reach this branch, allowing an unprivileged caller to trigger a NULL pointer dereference through KEYCTL_RESTRICT_KEYRING followed by add_key().
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000 KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:key_or_keyring_common (crypto/asymmetric_keys/restrict.c:205 crypto/asymmetric_keys/restrict.c:279) Call Trace: <TASK> __key_create_or_update (security/keys/key.c:884) key_create_or_update (security/keys/key.c:1021) __do_sys_add_key (security/keys/keyctl.c:134) do_syscall_64 (arch/x86/entry/common.c:52 arch/x86/entry/common.c:83) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) </TASK> Kernel panic - not syncing: Fatal exception
Reject an asymmetric restriction key without key IDs. A PKCS#8 private key cannot identify the signer of a candidate certificate and is not a valid trust anchor.
Patch / fix
- Linux Linux 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-99220
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-112538
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/889a2293a95f6c2880bf73b67f9b0af23251a128 commit
- git.kernel.org/stable/c/7f0728ba89624e25df2bb80ff59bbfb545060935 commit
- git.kernel.org/stable/c/2a40bdd4409567de4c2a141ac66439dc238af752 commit
- git.kernel.org/stable/c/1aa0c7aa4c2554a5b6d74ae1924508ca4718234b commit
- git.kernel.org/stable/c/33a078f04e264eb71aa9f209cb334e4010123818 commit
- git.kernel.org/stable/c/57e54b6939c6539d90a81c7e57531901d5991651 commit
- git.kernel.org/stable/c/9695df3b1db4ac4534274d38ee16e3b9b0bf910e 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-99220 updated cvss 5.5
kernel: kernel: Denial of Service via NULL pointer dereference in asymmetric key restriction
-
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-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 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8not 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.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/889a2293a95f6c2880bf73b67f9b0af23251a128
- git.kernel.org /stable/c/7f0728ba89624e25df2bb80ff59bbfb545060935
- git.kernel.org /stable/c/2a40bdd4409567de4c2a141ac66439dc238af752
- git.kernel.org /stable/c/1aa0c7aa4c2554a5b6d74ae1924508ca4718234b
- git.kernel.org /stable/c/33a078f04e264eb71aa9f209cb334e4010123818
- git.kernel.org /stable/c/57e54b6939c6539d90a81c7e57531901d5991651
- git.kernel.org /stable/c/9695df3b1db4ac4534274d38ee16e3b9b0bf910e
Sources
- CVE List CVE-2026-99220
- NVD CVE-2026-99220
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.