All reports
Medium

kernel: keys: make keyring key-chunk byte order agree with keyring_diff_objects()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-74566

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: keys: make keyring key-chunk byte order agree with keyring_diff_objects() keyring_get_key_chunk() loads description bytes into the index chunk low address first, while keyring_diff_objects() 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 keyring_diff_objects() 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.

A flaw was found in the Linux kernel's keys subsystem. An inconsistency in how key descriptions are processed by the keyring_get_key_chunk() and keyring_diff_objects() functions could allow a local attacker to create specially crafted key descriptions. These crafted descriptions might collide, potentially leading to unexpected system behavior or a denial of service.