CVE-2026-43405

libceph: Use u32 for non-negative values in ceph_monmap_decode()

HIGH
7.5
CVSS Score
Published: May 8, 2026 at 02:21 PM UTC
Updated: October 19, 2026 at 08:18 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.6%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: Use u32 for non-negative values in ceph_monmap_decode() This patch fixes unnecessary implicit conversions that change signedness of blob_len and num_mon in ceph_monmap_decode(). Currently blob_len and num_mon are (signed) int variables. They are used to hold values that are always non-negative and get assigned in ceph_decode_32_safe(), which is meant to assign u32 values. Both variables are subsequently used as unsigned values, and the value of num_mon is further assigned to monmap->num_mon, which is of type u32. Therefore, both variables should be of type u32. This is especially relevant for num_mon. If the value read from the incoming message is very large, it is interpreted as a negative value, and the check for num_mon > CEPH_MAX_MON does not catch it. This leads to the attempt to allocate a very large chunk of memory for monmap, which will most likely fail. In this case, an unnecessary attempt to allocate memory is performed, and -ENOMEM is returned instead of -EINVAL.

Affected

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

5.11 ≤ v < 5.15.2035.16 ≤ v < 6.1.1676.13 ≤ v < 6.18.196.19 ≤ v < 6.19.96.2 ≤ v < 6.6.1306.7 ≤ v < 6.12.785.117.07.0 rc17.0 rc27.0 rc3a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c
Vendor states this is fixed in 08bc6173fd611ad5a40f472bf5f15b92aea0fe40 (fixed)
Vendor states this is fixed in 5f2806684b05bd24d05c091083b8e2517ba8ffac (fixed)
Vendor states this is fixed in 770444611f047dbfd4517ec0bc1b179d40c2f346 (fixed)
Vendor states this is fixed in 86f7060cd638d6eb042e8ed780fb83a59ca0dcb3 (fixed)
Vendor states this is fixed in b268984ae88cb0dcd7a8e8263962c748448e26e8 (fixed)
Vendor states this is fixed in ba0a4df8c563536857dcbf7b4dbd0f2a15f57ace (fixed)
Vendor states this is fixed in ee5588e2bc41acb73f6676c0520420c107cd0140 (fixed)
Vendor states this is fixed in 5.11 (unaffected)
Vendor states this is fixed in 5.15.203 (unaffected)
Vendor states this is fixed in 6.1.167 (unaffected)
Vendor states this is fixed in 6.12.78 (unaffected)
Vendor states this is fixed in 6.18.19 (unaffected)
Vendor states this is fixed in 6.19.9 (unaffected)
Vendor states this is fixed in 6.6.130 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

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

StatusMODIFIED
CWE
CWE-908CWE-190

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