CVE-2026-89656

libceph: reject buckets with mismatched CRUSH ids

CRITICAL
9.8
CVSS Score
Published: September 11, 2026 at 07:45 PM UTC
Updated: October 19, 2026 at 09:18 AM 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
CRITICAL9.8
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: reject buckets with mismatched CRUSH ids crush_decode() stores bucket data by array slot, and the mapper later derives the per-bucket workspace index from the decoded bucket id. A malformed map can therefore make one bucket reuse another bucket's workspace by encoding an id different from -1 - slot. For uniform buckets, the second replica selection expands the source bucket's permutation into that aliased workspace buffer. If the source bucket is larger than the aliased bucket, the write runs past the smaller permutation array and can escape the kvmalloc'd CRUSH workspace. KASAN reports a slab OOB write of 4 bytes in bucket_perm_choose(). Reject buckets whose encoded id does not match their array slot. Valid CRUSH maps already use the canonical negative id corresponding to the bucket slot, so this restores the invariant expected by work->work[-1 - in->id] without changing valid map behavior.

Affected

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

4.1166a0e2d579dbec5c676cfe446234ffebb267c564
Vendor states this is fixed in 00562ccd4e88d092b9b851df50fad20442bfeb24 (fixed)
Vendor states this is fixed in 3516a4131c4e45d62ee4e42e82c36930e8c1fbbd (fixed)
Vendor states this is fixed in 3cde4a8302301679937474a5f7a851394cc1bd11 (fixed)
Vendor states this is fixed in 4aeb93daadf388e72073abc204312dd364eeb30a (fixed)
Vendor states this is fixed in 6e5c6ce252b1eccfd41670a5cf95ab44f7ba7022 (fixed)
Vendor states this is fixed in 79900d978158b2d80eef952fc41b9e4dc58d7b83 (fixed)
Vendor states this is fixed in baad5875fdd2f5e248250fc3519bb045d64f1716 (fixed)
Vendor states this is fixed in ee59040d6ed1a5f8d10d27174b8f32c90ca8e89a (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (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.

SSVC — Action Prioritization

SSVCNo known exploitAutomatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

9.8CRITICALLinux
Vector?

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