CVE-2026-68154
Linux kernel vulnerability
- Published10 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/05f90284223381005d6bcddab3fda4a97f9c3401
- https://git.kernel.org/stable/c/146461f09565afe3665e65b0423d3d6b0fe806c5
- https://git.kernel.org/stable/c/3b2f1937f5fce8b7dd5432e7693e3cc8b5eece56
- https://git.kernel.org/stable/c/70998f91030ee083ecb336a1dff0701c20a38081
- https://git.kernel.org/stable/c/80fc40e11cda1b5d990a3f69c6efa344fb5cd987
- https://git.kernel.org/stable/c/826cd1de5802fd392922785f9b64d76e65d2a100
- https://git.kernel.org/stable/c/952ca5dc99913d169263f59fd689f586729a13c1
- https://git.kernel.org/stable/c/b8a9fb6bf806f9c4891e71ae1beab0c07c23a877
Frequently asked
Is CVE-2026-68154 being actively exploited?
CVE-2026-68154 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.71%.
How severe is CVE-2026-68154?
CVE-2026-68154 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.71% probability of exploitation.
How do I fix CVE-2026-68154?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-68154 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.