CVE-2026-74566

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

N/A
Published: August 15, 2026 at 12:28 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.3 ≤ v < 5.10.2655.3 ≤ v < 5.15.2165.3 ≤ v < 6.1.1835.3 ≤ v < 6.12.1035.3 ≤ v < 6.18.445.3 ≤ v < 6.6.1515.3 ≤ v < 7.1.85.3 ≤ v < 7.25.3f771fde82051976a6fc0fd570f8b86de4a92124b
Vendor states this is fixed in 3d9f16c0b643ceac305526b2e2fe25c2c6166926 (fixed)
Vendor states this is fixed in 414bcf37d81ce9b3823aabc06b04c97fdcbe489b (fixed)
Vendor states this is fixed in 58565eef0f8d861aae92abfb7658458d661cee17 (fixed)
Vendor states this is fixed in 7269df3e7fcfa308e6a456305162f7788747bdbd (fixed)
Vendor states this is fixed in 7e5397a3fed0dee7779bd084bec3c0584db3c930 (fixed)
Vendor states this is fixed in abe43c661efb753d5ee35ad8ace4bbb16fa9afd0 (fixed)
Vendor states this is fixed in bd0f976ef89dce6db458bf75bc2cf51127becc41 (fixed)
Vendor states this is fixed in f81920917074e3c4ad4fba06fe8c56738d010606 (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.3 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card