Invalid kernel read via keyring ownership race
Published Nov 2, 2026 · Updated Nov 2, 2026
Use-after-free in Linux keyring lookup allows local users to trigger an invalid kernel read via a session-keyring join. The find_keyring_by_name() function reads keyring->user->uid while its lock protects the keyring but not the separately allocated owner account. Triggering requires a concurrent privileged KEYCTL_CHOWN that frees the old account's last reference; the reported result is a four-byte read from freed memory, with no further impact established.
Summary
What happened
Use-after-free in Linux keyring lookup allows local users to trigger an invalid kernel read via a session-keyring join. The find_keyring_by_name() function reads keyring->user->uid while its lock protects the keyring but not the separately allocated owner account. Triggering requires a concurrent privileged KEYCTL_CHOWN that frees the old account's last reference; the reported result is a four-byte read from freed memory, with no further impact established.
The record
- CVE
- CVE-2026-99226
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
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=2.6.30
- Affected versionversion=2ea190d0a006ce5218baa6e798512652446a605a <0b865fa477d94ac96c26848aab1fd176397de3f6
- Affected versionversion=2ea190d0a006ce5218baa6e798512652446a605a <40b12b93ae4ab9e22c3d571e9b09fd08afad53f6
- Affected versionversion=2ea190d0a006ce5218baa6e798512652446a605a <5c6a9512887a6cc694d594d9c0b57c0841d215b5
- Affected versionversion=2ea190d0a006ce5218baa6e798512652446a605a <6763329f673d261641c79212abf773af77b2c922
- Affected versionversion=2ea190d0a006ce5218baa6e798512652446a605a <77249d4b1bb5ad43552b7023c4a0978937aa7a56
- Affected versionversion=2ea190d0a006ce5218baa6e798512652446a605a <aa03c8fb4334f14d218020f7431debf2b7766865
- Affected versionversion=2ea190d0a006ce5218baa6e798512652446a605a <b0830a26e2c3008a6e21863126b4a0e68b2761cd
- Affected versionversion=2ea190d0a006ce5218baa6e798512652446a605a <c9664f780f861dd9f11f120c7a03ed0993671ebb
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
No sourced classifications are available.
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