Restriction bypass via stale keyring restriction snapshot
Published Oct 23, 2026 · Updated Oct 23, 2026
A race in Linux keyring creation allows local users to bypass reject-all restrictions via concurrent add_key() and restriction calls. __key_create_or_update() reads keyring->restrict_link before acquiring the destination semaphore, then links an attacker-supplied key using a stale NULL snapshot after restriction installation completes. Exploitation requires write permission on the destination keyring and winning the race; the demonstrated consequence is insertion of a prohibited key, not arbitrary code execution.
Summary
What happened
A race in Linux keyring creation allows local users to bypass reject-all restrictions via concurrent add_key() and restriction calls. __key_create_or_update() reads keyring->restrict_link before acquiring the destination semaphore, then links an attacker-supplied key using a stale NULL snapshot after restriction installation completes. Exploitation requires write permission on the destination keyring and winning the race; the demonstrated consequence is insertion of a prohibited key, not arbitrary code execution.
The record
- CVE
- CVE-2026-99040
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=4.7
- Affected versionversion=5ac7eace2d00eab5ae0e9fdee63e38aee6001f7c <11516a0c402a6c1fa52254aa70d8d65fb921e59e
- Affected versionversion=5ac7eace2d00eab5ae0e9fdee63e38aee6001f7c <305f1828b871dd46bf41addeb6f11d2c162dcb25
- Affected versionversion=5ac7eace2d00eab5ae0e9fdee63e38aee6001f7c <da0b595d8e6e2dd798f6e34e09dc51a13b888514
- Affected versionversion=5ac7eace2d00eab5ae0e9fdee63e38aee6001f7c <dd3ea3fcba7c75493760cdbccd35f029597e8d5e
- Affected versionversion=5ac7eace2d00eab5ae0e9fdee63e38aee6001f7c <f99399b48e3edd6851fac34cd329bab9f1f33baf
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