CVE-2026-68155

libceph: Reject monmaps advertising zero monitors

HIGH
7.5
CVSS Score
Published: August 10, 2026 at 11:59 AM UTC
Updated: October 19, 2026 at 09:17 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
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: Reject monmaps advertising zero monitors A message of type CEPH_MSG_MON_MAP contains a monmap that is sent from a monitor to the client. This monmap contains information about the existing monitors in the cluster. Currently, a monmap indicating that there are zero monitors in the cluster is treated as valid. However, it is impossible to have zero monitors in the cluster and still receive a valid monmap from a monitor. Therefore, such a monmap must be corrupted and should be treated as invalid. Furthermore, a monmap with a monitor count of zero can subsequently crash the client when attempting to open a session with a monitor in __open_session(). This happens because the "BUG_ON(monc->monmap->num_mon < 1)" assertion in pick_new_mon() is triggered. This patch extends a check in ceph_monmap_decode() to also reject arriving mon_maps with num_mon == 0 rather than only with num_mon > CEPH_MAX_MON. [ idryomov: drop "log output for unusual values of num_mon" part ]

Affected

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

2.6.34ba75bb98cfb93b62c54af25bf67ff90857264bbe
Vendor states this is fixed in 0591a15815b498be628a937146e44487d599ba33 (fixed)
Vendor states this is fixed in 3b249546f59c3d6d3592c10657f82bc3f1faa07c (fixed)
Vendor states this is fixed in 40480eee361ed9676b3f844d532ac28b47251634 (fixed)
Vendor states this is fixed in ba5f0015bfd376d764163045a61c17be75f44dae (fixed)
Vendor states this is fixed in caf082ef8609a6ac26159ce115f55ab7d00231a3 (fixed)
Vendor states this is fixed in cd0d41bc569632eaaeccde9d2a6bc919ec00c407 (fixed)
Vendor states this is fixed in e3ccd4ecab09b22f507f49cb7ed9990c7158ceab (fixed)
Vendor states this is fixed in e67e8b694872c9bc66996040f9de9242f6236ed9 (fixed)
Vendor states this is fixed in 2.6.34 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (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.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

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

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-20

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