CVE-2026-99220: Linux kernel · asymmetric_keys: reject trust keys without IDs
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 889a2293a95f6c2880bf73b67f9b0af23251a128 : patch Linux kernel soon.
Data as of 2 Nov 2026, 16:32 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 889a2293a95f6c2880bf73b67f9b0af23251a128, 57e54b6939c6539d90a81c7e57531901d5991651, 33a078f04e264eb71aa9f209cb334e4010123818 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in specific Linux kernel commits. Users should update their Linux kernel to a version including these fixes to prevent exploitation. No additional mitigation steps are indicated or required beyond applying the official fix.
Description
A vulnerability in the Linux kernel asymmetric_keys subsystem allowed unprivileged users to trigger a NULL pointer dereference via trust keys without IDs. This flaw occurs because the PKCS#8 parser leaves the asym_key_ids payload empty, but the kernel code unconditionally dereferences this slot when applying key restrictions. This can cause a kernel panic due to a general protection fault. The issue has been fixed by rejecting asymmetric restriction keys that lack key IDs, as PKCS#8 private keys cannot serve as valid trust anchors.
References
- git.kernel.org/stable/c/889a2293a95f6c2880bf73b67f9b0af23251a128 (opens in a new tab)
- git.kernel.org/stable/c/7f0728ba89624e25df2bb80ff59bbfb545060935 (opens in a new tab)
- git.kernel.org/stable/c/2a40bdd4409567de4c2a141ac66439dc238af752 (opens in a new tab)
- git.kernel.org/stable/c/1aa0c7aa4c2554a5b6d74ae1924508ca4718234b (opens in a new tab)
- git.kernel.org/stable/c/33a078f04e264eb71aa9f209cb334e4010123818 (opens in a new tab)
- git.kernel.org/stable/c/57e54b6939c6539d90a81c7e57531901d5991651 (opens in a new tab)