CVE-2026-74566: keys: make keyring key-chunk byte order agree with keyring_diff_objects()
In the Linux kernel, the following vulnerability has been resolved:
keys: make keyring key-chunk byte order agree with keyringdiffobjects()
keyringgetkeychunk() loads description bytes into the index chunk low address first, while keyringdiffobjects() numbers the first differing bit from the low end and folds the absolute byte index into the level without removing the inline-prefix offset the level already carries. The two disagree on byte order and bit position, so the array can be told two keys first differ at a bit that does not differ in the chunk the walker uses, letting crafted descriptions collide into one node.
Load the chunk in the order keyringdiffobjects() assumes and drop the inline-prefix length when folding the byte index into the level. This only changes the in-memory ordering used to place keys within a keyring; add, search and read of non-colliding keys are unaffected.
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability risk level of CVE-2026-74566?
The risk level of CVE-2026-74566 is 37, indicating a moderate severity.
How do I mitigate CVE-2026-74566?
To mitigate CVE-2026-74566, ensure you are running the latest version of the Linux kernel that addresses this vulnerability.
What does CVE-2026-74566 affect?
CVE-2026-74566 affects the keyring functionality within the Linux kernel, specifically the byte order used in key-chunks.
When was CVE-2026-74566 published?
CVE-2026-74566 was published on August 15, 2026.
What components are involved in the CVE-2026-74566 vulnerability?
CVE-2026-74566 involves the keyring_get_key_chunk() and keyring_diff_objects() functions in the Linux kernel.