Kernel panic via missing trust-key ID validation
Published Nov 2, 2026 · Updated Nov 2, 2026
NULL pointer dereference in Linux asymmetric key restrictions allows local users to crash the kernel through crafted keyring operations. The key_or_keyring_common() function dereferences asym_key_ids even though the PKCS#8 parser leaves that payload empty. An unprivileged caller supplies a PKCS#8 restriction key through KEYCTL_RESTRICT_KEYRING followed by add_key(); both plain and :chain restrictions reach the faulty branch, and the reported failure is a kernel panic.
Summary
What happened
NULL pointer dereference in Linux asymmetric key restrictions allows local users to crash the kernel through crafted keyring operations. The key_or_keyring_common() function dereferences asym_key_ids even though the PKCS#8 parser leaves that payload empty. An unprivileged caller supplies a PKCS#8 restriction key through KEYCTL_RESTRICT_KEYRING followed by add_key(); both plain and :chain restrictions reach the faulty branch, and the reported failure is a kernel panic.
The record
- CVE
- CVE-2026-99220
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 2, 2026CVE publishedPublication date reported by the CVE source.
- Nov 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3c58b2362ba828ee2970c66c6a6fd7b04fde4413 <1aa0c7aa4c2554a5b6d74ae1924508ca4718234b
- Affected versionversion=3c58b2362ba828ee2970c66c6a6fd7b04fde4413 <2a40bdd4409567de4c2a141ac66439dc238af752
- Affected versionversion=3c58b2362ba828ee2970c66c6a6fd7b04fde4413 <33a078f04e264eb71aa9f209cb334e4010123818
- Affected versionversion=3c58b2362ba828ee2970c66c6a6fd7b04fde4413 <57e54b6939c6539d90a81c7e57531901d5991651
- Affected versionversion=3c58b2362ba828ee2970c66c6a6fd7b04fde4413 <7f0728ba89624e25df2bb80ff59bbfb545060935
- Affected versionversion=3c58b2362ba828ee2970c66c6a6fd7b04fde4413 <889a2293a95f6c2880bf73b67f9b0af23251a128
- Affected versionversion=4.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us