CVE-2026-43405

published 8 May 2026 · updated 13 Nov 2026

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

7.5HighCVSS 7.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 5.15.203, Kernel 6.1.167, Kernel 6.18.19 and 10 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5.11 <5.15.203, >=5.16 <6.1.167, >=6.13 <6.18.19, >=6.19 <6.19.9, >=6.2 <6.6.130, >=6.7 <6.12.78, =7.0, >=a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c <5f2806684b05bd24d05c091083b8e2517ba8ffac, >=a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c <770444611f047dbfd4517ec0bc1b179d40c2f346, >=a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c <86f7060cd638d6eb042e8ed780fb83a59ca0dcb3, >=a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c <b268984ae88cb0dcd7a8e8263962c748448e26e8, >=a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c <ba0a4df8c563536857dcbf7b4dbd0f2a15f57ace, >=a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c <ee5588e2bc41acb73f6676c0520420c107cd0140, =5.11, >=a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c <08bc6173fd611ad5a40f472bf5f15b92aea0fe405.15.203, 6.1.167, 6.18.19, 6.19.9, 6.6.130, 6.12.78, 5f2806684b05bd24d05c091083b8e2517ba8ffac, 770444611f047dbfd4517ec0bc1b179d40c2f346, 86f7060cd638d6eb042e8ed780fb83a59ca0dcb3, b268984ae88cb0dcd7a8e8263962c748448e26e8, ba0a4df8c563536857dcbf7b4dbd0f2a15f57ace, ee5588e2bc41acb73f6676c0520420c107cd0140, 08bc6173fd611ad5a40f472bf5f15b92aea0fe40
linux-kernel: Kernel>=5.11.0 <5.15.203, >=5.16.0 <6.1.167, >=6.13.0 <6.18.19, >=6.19.0 <6.19.9, >=6.2.0 <6.6.130, >=6.7.0 <6.12.785.15.203, 6.1.167, 6.18.19, 6.19.9, 6.6.130, 6.12.78

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-43405 severity on Zeptric[![CVE-2026-43405](https://zeptric.io/badge/cve/CVE-2026-43405.svg)](https://zeptric.io/cve/CVE-2026-43405)