From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68154: libceph: reject zero bucket types in crush_decode
Date: Mon, 10 Aug 2026 13:57:51 +0200 [thread overview]
Message-ID: <2026081002-CVE-2026-68154-8d92@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
libceph: reject zero bucket types in crush_decode
CRUSH bucket type 0 is reserved for devices. The mapper relies on
that invariant and uses type 0 to identify leaf devices.
If crush_decode() accepts a bucket with type 0, a malformed CRUSH map
can make the mapper treat a negative bucket ID as a device and pass it
to is_out(), which then indexes the OSD weight array with a negative
value.
Reject zero bucket types while decoding the CRUSH map so the invalid
state never reaches the mapper.
The Linux kernel CVE team has assigned CVE-2026-68154 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.34 with commit f24e9980eb860d8600cbe5ef3d2fd9295320d229 and fixed in 6.6.148 with commit b8a9fb6bf806f9c4891e71ae1beab0c07c23a877
Issue introduced in 2.6.34 with commit f24e9980eb860d8600cbe5ef3d2fd9295320d229 and fixed in 6.12.101 with commit 826cd1de5802fd392922785f9b64d76e65d2a100
Issue introduced in 2.6.34 with commit f24e9980eb860d8600cbe5ef3d2fd9295320d229 and fixed in 6.18.42 with commit 3b2f1937f5fce8b7dd5432e7693e3cc8b5eece56
Issue introduced in 2.6.34 with commit f24e9980eb860d8600cbe5ef3d2fd9295320d229 and fixed in 7.1.6 with commit 70998f91030ee083ecb336a1dff0701c20a38081
Issue introduced in 2.6.34 with commit f24e9980eb860d8600cbe5ef3d2fd9295320d229 and fixed in 7.2-rc5 with commit 05f90284223381005d6bcddab3fda4a97f9c3401
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-68154
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/ceph/osdmap.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/b8a9fb6bf806f9c4891e71ae1beab0c07c23a877
https://git.kernel.org/stable/c/826cd1de5802fd392922785f9b64d76e65d2a100
https://git.kernel.org/stable/c/3b2f1937f5fce8b7dd5432e7693e3cc8b5eece56
https://git.kernel.org/stable/c/70998f91030ee083ecb336a1dff0701c20a38081
https://git.kernel.org/stable/c/05f90284223381005d6bcddab3fda4a97f9c3401
reply other threads:[~2026-08-10 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081002-CVE-2026-68154-8d92@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.