Is there a patch available for CVE-2026-99226?

Yes, a patch is available for CVE-2026-99226. Update the affected software to the latest version immediately.

Linux CVE-2026-99226

EUVD-2026-115268

2026-11-02 Linux

GHSA-9pjv-mg4c-3j9m

Information Disclosure Linux

View

Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).

Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

In the Linux kernel, the following vulnerability has been resolved:

keys: Avoid the owner account dereference in named keyring lookup

Named keyring lookup must keep the storage containing the owner UID alive through the namespace mapping check. find_keyring_by_name() reads keyring->user->uid under keyring_name_lock, but that lock protects the keyring's name entry and allocation, not its separate key_user.

A named session-keyring join can overlap a privileged KEYCTL_CHOWN on another CPU. If the keyring holds the last reference to its old dynamic key_user and the ownership transfer succeeds, the following ordering is possible:

Named join Chown find_keyring_by_name() keyctl_chown_key() read_lock(keyring_name_lock) down_write(key->sem) load old keyring->user replace key->user and key->uid up_write(key->sem) key_put(key) key_user_put(old user): free read old user->uid read_unlock(keyring_name_lock)

Chown neither takes keyring_name_lock nor key_session_mutex, so it can free the old account between the pointer load and the UID read. The lookup then reads freed memory even though the keyring itself is alive.

Use keyring->uid for the mapping check. key_alloc() initializes this inline owner UID and keyctl_chown_key() updates it on chown. The existing name lock keeps its containing keyring allocated throughout the check, so lookup no longer depends on the account's lifetime. This also matches the owner UID used by the permission check.

KASAN report as below:

BUG: KASAN: slab-use-after-free in find_keyring_by_name+0x577/0x5d0 Read of size 4 at addr ffff8881128ae2ec by task keycase/500

Affected VersionsENISA

Linux 2.6.30

Linux patch: 6.1.191

Linux patch: 6.18.60

Linux 2ea190d0a006ce5218baa6e798512652446a605a <77249d4b1bb5ad43552b7023c4a0978937aa7a56

Linux 2ea190d0a006ce5218baa6e798512652446a605a <c9664f780f861dd9f11f120c7a03ed0993671ebb

Linux 2ea190d0a006ce5218baa6e798512652446a605a <aa03c8fb4334f14d218020f7431debf2b7766865

Linux patch: 6.6.161

Linux patch: 7.3.1

Linux patch: 7.2.14

Linux 2ea190d0a006ce5218baa6e798512652446a605a <5c6a9512887a6cc694d594d9c0b57c0841d215b5

Linux patch: 6.12.115

Linux 2ea190d0a006ce5218baa6e798512652446a605a <b0830a26e2c3008a6e21863126b4a0e68b2761cd

Linux 2ea190d0a006ce5218baa6e798512652446a605a <6763329f673d261641c79212abf773af77b2c922

Linux patch: 0

Linux patch: 5.10.273

Linux 2ea190d0a006ce5218baa6e798512652446a605a <40b12b93ae4ab9e22c3d571e9b09fd08afad53f6

Linux 2ea190d0a006ce5218baa6e798512652446a605a <0b865fa477d94ac96c26848aab1fd176397de3f6

Linux patch: 5.15.224

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Lifecycle Timeline

Patch available

Nov 02, 2026 - 17:18 EUVD

CVE Published

Nov 02, 2026 - 16:06 cve.org

UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score

0.2%

Top 94% exploitable

Data Quality

1 sources

Confidence: Low

EUVD

CVE.org

EPSS

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity Not scored yet

CISA KEV No

Public POC No

EPSS 0.2%

Patch available Yes

Active threat No

Deciding rule

No CVSS yet + weak signal (CWE or non-zero EPSS)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.