Skip to main content
VulnerabilityPublished Updated

CVE-2026-68155: Linux kernel · libceph: Reject monmaps advertising zero monitors

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in e67e8b694872c9bc66996040f9de9242f6236ed9 : patch Linux kernel soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in e67e8b694872c9bc66996040f9de9242f6236ed9, e3ccd4ecab09b22f507f49cb7ed9990c7158ceab, cd0d41bc569632eaaeccde9d2a6bc919ec00c407 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ba75bb98cfb93b62c54af25bf67ff90857264bbe, < e67e8b694872c9bc66996040f9de9242f6236ed9
Fixed in
  • e67e8b694872c9bc66996040f9de9242f6236ed9
LinuxLinuxAffected
  • ≥ ba75bb98cfb93b62c54af25bf67ff90857264bbe, < e3ccd4ecab09b22f507f49cb7ed9990c7158ceab
Fixed in
  • e3ccd4ecab09b22f507f49cb7ed9990c7158ceab
LinuxLinuxAffected
  • ≥ ba75bb98cfb93b62c54af25bf67ff90857264bbe, < cd0d41bc569632eaaeccde9d2a6bc919ec00c407
Fixed in
  • cd0d41bc569632eaaeccde9d2a6bc919ec00c407
LinuxLinuxAffected
  • ≥ ba75bb98cfb93b62c54af25bf67ff90857264bbe, < caf082ef8609a6ac26159ce115f55ab7d00231a3
Fixed in
  • caf082ef8609a6ac26159ce115f55ab7d00231a3
LinuxLinuxAffected
  • ≥ ba75bb98cfb93b62c54af25bf67ff90857264bbe, < ba5f0015bfd376d764163045a61c17be75f44dae
Fixed in
  • ba5f0015bfd376d764163045a61c17be75f44dae
LinuxLinuxAffected
  • ≥ ba75bb98cfb93b62c54af25bf67ff90857264bbe, < 40480eee361ed9676b3f844d532ac28b47251634
Fixed in
  • 40480eee361ed9676b3f844d532ac28b47251634

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 ]

References

Community reviews

Loading reviews…