Kernel-address disclosure via predictable keyring ordering
Published Nov 2, 2026 · Updated Nov 2, 2026
Information disclosure in Linux keyrings allows local users to recover the kernel image address through KEYCTL_READ ordering. In security/keys/keyring.c, hash_key_type_and_desc hashes kernel pointers with attacker-chosen descriptions, and KEYCTL_READ exposes the resulting traversal order. Exploitation requires access to the key retention service and a keyring that permits key insertion and reading; the disclosed effect is a KASLR bypass, not privilege escalation.
Summary
What happened
Information disclosure in Linux keyrings allows local users to recover the kernel image address through KEYCTL_READ ordering. In security/keys/keyring.c, hash_key_type_and_desc hashes kernel pointers with attacker-chosen descriptions, and KEYCTL_READ exposes the resulting traversal order. Exploitation requires access to the key retention service and a keyring that permits key insertion and reading; the disclosed effect is a KASLR bypass, not privilege escalation.
The record
- CVE
- CVE-2026-99223
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- 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=3.13
- Affected versionversion=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <13fc051269d670810d9e314061b61c6dd06116a0
- Affected versionversion=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <61ac0585d9f4344d3dfb84b5edff1fee7d532897
- Affected versionversion=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <8451d4a4c43127c3b9fdf9fc9ff3fea5539a61f9
- Affected versionversion=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <84f7c699f8d139f743c7dc11ef41d085690955bb
- Affected versionversion=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <9ebe824d55983c9f063a2c9ef1a08b29812d406f
- Affected versionversion=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <9f084ef0beb68091e96ab96f0e95579aac8a77f9
- Affected versionversion=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <a113eba06bd1183c614d7994864d6e7054140cb9
- Affected versionversion=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <e108b22999edbc6f431466baf6b2016c19b7ed31
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