CVE-2026-99223

published 2 Nov 2026 · updated 20 Nov 2026

keys: make keyring indexes independent of kernel addresses

3.3LowCVSS 3.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e108b22999edbc6f431466baf6b2016c19b7ed31, Kernel 13fc051269d670810d9e314061b61c6dd06116a0, Kernel 61ac0585d9f4344d3dfb84b5edff1fee7d532897 and 14 more.

In the Linux kernel, the following vulnerability has been resolved: keys: make keyring indexes independent of kernel addresses KEYCTL_READ returns the serial numbers in a keyring in associative-array traversal order. The first word of the index is a public, deterministic hash of the type pointer, domain pointer and description. An unprivileged user can therefore insert keys with known descriptions, predict their order for each possible KASLR slide, and recover the kernel image address. On an x86-64 build with 16 MiB alignment, 45 user keys suffice to distinguish the candidate slides. Remove the addresses from the whole index, not just its first hash word. Assign each key type and domain a nonzero 64-bit ID and hash those IDs and the description with a once-initialized SipHash key. Use the full IDs in the later index chunks as well. Truncating or hashing the IDs there would lose the guarantee that distinct type/domain/description tuples have a differing index bit. Allocate IDs lazily since private key types need not be registered. Cache them in the index key so tree walks and copies of an existing index do not need to dereference a type descriptor that may have been unregistered. Keep the 32-bit chunk layout and diff_objects() bit offsets consistent, and retain the separate root slot for keyrings used by recursive search. The key comparison, permissions and userspace data format are unchanged; only the address-dependent in-memory ordering is replaced.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <e108b22999edbc6f431466baf6b2016c19b7ed31, >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <13fc051269d670810d9e314061b61c6dd06116a0, >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <61ac0585d9f4344d3dfb84b5edff1fee7d532897, >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <8451d4a4c43127c3b9fdf9fc9ff3fea5539a61f9, >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <84f7c699f8d139f743c7dc11ef41d085690955bb, >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <9ebe824d55983c9f063a2c9ef1a08b29812d406f, >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <9f084ef0beb68091e96ab96f0e95579aac8a77f9, >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <a113eba06bd1183c614d7994864d6e7054140cb9, >=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69 <de891c73c1cf41ac8de12c07fa2c84d6a912ad0c, =3.13e108b22999edbc6f431466baf6b2016c19b7ed31, 13fc051269d670810d9e314061b61c6dd06116a0, 61ac0585d9f4344d3dfb84b5edff1fee7d532897, 8451d4a4c43127c3b9fdf9fc9ff3fea5539a61f9, 84f7c699f8d139f743c7dc11ef41d085690955bb, 9ebe824d55983c9f063a2c9ef1a08b29812d406f, 9f084ef0beb68091e96ab96f0e95579aac8a77f9, a113eba06bd1183c614d7994864d6e7054140cb9, de891c73c1cf41ac8de12c07fa2c84d6a912ad0c
linux-kernel: Kernel>=5.11.0 <5.15.224, >=5.16.0 <6.1.191, >=6.13.0 <6.18.60, >=6.19.0 <7.2.14, >=6.2.0 <6.6.161, >=6.7.0 <6.12.115, >=7.3.0 <7.3.1, >=3.13.0 <5.10.2735.15.224, 6.1.191, 6.18.60, 7.2.14, 6.6.161, 6.12.115, 7.3.1, 5.10.273

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99223 severity on Zeptric[![CVE-2026-99223](https://zeptric.io/badge/cve/CVE-2026-99223.svg)](https://zeptric.io/cve/CVE-2026-99223)