Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-99220: asymmetric_keys: reject trust keys without IDs

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Fixed version: Linux Linux 1aa0c7aa4c2554a5b6d74ae1924508ca4718234b, 2a40bdd4409567de4c2a141ac66439dc238af752, 33a078f04e264eb71aa9f209cb334e4010123818.

Low priority for now. Upgrade to Linux Linux 1aa0c7aa4c2554a5b6d74ae1924508ca4718234b, 2a40bdd4409567de4c2a141ac66439dc238af752, 33a078f04e264eb71aa9f209cb334e4010123818 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Nov 2, 2026
Updated
Nov 3, 2026
EPSS
0.1% · 1th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99220

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.20affected
    • 3c58b2362ba828ee2970c66c6a6fd7b04fde4413 and later · before 889a2293a95f6c2880bf73b67f9b0af23251a128affected · git
    • 3c58b2362ba828ee2970c66c6a6fd7b04fde4413 and later · before 7f0728ba89624e25df2bb80ff59bbfb545060935affected · git
    • 3c58b2362ba828ee2970c66c6a6fd7b04fde4413 and later · before 2a40bdd4409567de4c2a141ac66439dc238af752affected · git
    • 3c58b2362ba828ee2970c66c6a6fd7b04fde4413 and later · before 1aa0c7aa4c2554a5b6d74ae1924508ca4718234baffected · git
    • 3c58b2362ba828ee2970c66c6a6fd7b04fde4413 and later · before 33a078f04e264eb71aa9f209cb334e4010123818affected · git
    • 3c58b2362ba828ee2970c66c6a6fd7b04fde4413 and later · before 57e54b6939c6539d90a81c7e57531901d5991651affected · git
    • 3c58b2362ba828ee2970c66c6a6fd7b04fde4413 and later · before 9695df3b1db4ac4534274d38ee16e3b9b0bf910eaffected · git
    • before 4.20not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.115-16.12.115-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99218Nov 2, 2026 · coredump: hold RCU while releasing parked threads
    28Monitor
  • ← EarlierCVE-2026-99219Nov 2, 2026 · ftrace: Initialize modname and offset in print_rec()
    0Monitor
  • Later →CVE-2026-99221Nov 2, 2026 · keys/trusted_keys: return immediately after TPM unseal failure
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1aa0c7aa4c2554a5b6d74ae1924508ca4718234bVendor (CNA)
Linux Linux2a40bdd4409567de4c2a141ac66439dc238af752Vendor (CNA)
Linux Linux33a078f04e264eb71aa9f209cb334e4010123818Vendor (CNA)
Linux Linux57e54b6939c6539d90a81c7e57531901d5991651Vendor (CNA)
Linux Linux7f0728ba89624e25df2bb80ff59bbfb545060935Vendor (CNA)
Linux Linux889a2293a95f6c2880bf73b67f9b0af23251a128Vendor (CNA)
Linux Linux9695df3b1db4ac4534274d38ee16e3b9b0bf910eVendor (CNA)
debian:linux6.12.115-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 5, 2026+3 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓
  2. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records