Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-99225: keys: Check the authorization payload in process keyring searches

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.18% (FIRST EPSS).
  • Fixed version: Linux Linux 0a0ec45bf577a9b4d4960567f20d3877ef480de9, 14fb6fad526b35a7ebd121f1dd313abe652e0aa6, 26949c2e4c461e9e620e935bc22717f36a40b615.

Low priority for now. Upgrade to Linux Linux 0a0ec45bf577a9b4d4960567f20d3877ef480de9, 14fb6fad526b35a7ebd121f1dd313abe652e0aa6, 26949c2e4c461e9e620e935bc22717f36a40b615 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: keys: Check the authorization payload in process keyring searches An authorization payload and its saved credentials must remain valid while search_process_keyrings_rcu() searches the requestor's keyrings. The function validates the authorization key, then separately loads payload.data[0] and unconditionally reads rka->cred. Validation does not prevent request_key_auth_revoke() from clearing the payload. A request-key helper can assume authority and fork a descendant that inherits the authorization key. If the descendant misses in its own keyrings, it falls back to the saved requestor credentials. Successful target instantiation invalidates the authorization key without clearing the payload. After the helper exits, UMH_WAIT_PROC returns to the requester, which calls complete_request_key() and revokes that key. With the descendant paused after validation, the paths can interleave as follows: 1. The descendant enters search_process_keyrings_rcu() under RCU and key_validate() succeeds. 2. The helper instantiates the target, invalidates the authorization key, and exits. 3. The requester resumes from UMH_WAIT_PROC, calls complete_request_key(), and revokes the authorization key. request_key_auth_revoke() sets its payload pointer to NULL. 4. The descendant loads NULL and dereferences rka->cred. This NULL dereference can oops the kernel. RCU delays payload disposal but does not prevent the pointer from being cleared. Load the payload with dereference_key_rcu() and require a non-NULL result before validating the authorization key and searching its saved credentials. A non-NULL payload and its credentials remain alive for the caller's RCU read-side section; a cleared payload skips the fallback search and follows the existing error selection. KASAN report as below: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] RIP: 0010:search_process_keyrings_rcu+0x32b/0x790

—No exploit Fix available
Published
Nov 2, 2026
Updated
Nov 3, 2026
EPSS
0.1% · 7th 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-99225

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

    • 5.3affected
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before 14fb6fad526b35a7ebd121f1dd313abe652e0aa6affected · git
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before 458cf9715af6aff3ac8d2ec60bd59e9d6236fd0faffected · git
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before 7d3d2fffe933e538472ccafe5bbc7109488b9ce3affected · git
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before 26949c2e4c461e9e620e935bc22717f36a40b615affected · git
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before 984a178d54515779a1bee100b92a6cee8777c830affected · git
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before b86db7993051d05810601654e886a1e78e1fa495affected · git
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before b4dfda438fee3c6faa15d9b421c373de6a0e476faffected · git
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before 49f4e768540d25d8852ef750313afda6a4774871affected · git
    • e59428f721ee096d8a020504ea908a6f0d952735 and later · before 0a0ec45bf577a9b4d4960567f20d3877ef480de9affected · git

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-99223Nov 2, 2026 · keys: make keyring indexes independent of kernel addresses
    0Monitor
  • ← EarlierCVE-2026-99224Nov 2, 2026 · keys: Protect the type name while describing a key
    28Monitor
  • Later →CVE-2026-99226Nov 2, 2026 · keys: Avoid the owner account dereference in named keyring lookup
    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 Linux0a0ec45bf577a9b4d4960567f20d3877ef480de9Vendor (CNA)
Linux Linux14fb6fad526b35a7ebd121f1dd313abe652e0aa6Vendor (CNA)
Linux Linux26949c2e4c461e9e620e935bc22717f36a40b615Vendor (CNA)
Linux Linux458cf9715af6aff3ac8d2ec60bd59e9d6236fd0fVendor (CNA)
Linux Linux49f4e768540d25d8852ef750313afda6a4774871Vendor (CNA)
Linux Linux7d3d2fffe933e538472ccafe5bbc7109488b9ce3Vendor (CNA)
Linux Linux984a178d54515779a1bee100b92a6cee8777c830Vendor (CNA)
Linux Linuxb4dfda438fee3c6faa15d9b421c373de6a0e476fVendor (CNA)
Linux Linuxb86db7993051d05810601654e886a1e78e1fa495Vendor (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+2 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 (8 more)

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

All records