Vulnerability · Published May 8, 2026 · Assigned by Linux
CVE-2026-43405libceph: Use u32 for non-negative values in ceph_monmap_decode()
High 7.5
In plain English
A high-severity integer overflow in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 49% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.170-1 | DEBIAN-CVE-2026-43405 |
| Debian:13 | linux | 6.12.85-1 | DEBIAN-CVE-2026-43405 |
| Debian:14 | linux | 6.19.10-1 | DEBIAN-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux | 5.15.0-186.196 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux | 6.8.0-136.136 | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1112.119 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1061.64 | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux-aws | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1061.64~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1117.126 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1063.71 | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1063.71~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1117.126 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1062.69 | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1062.69~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1112.122 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1064.72 | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux-gcp | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1064.72~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1108.114 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1059.67 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1095.103 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1046.50 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-136.136~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1106.110 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1061.62 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1061.62~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1107.113 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1104.109 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-184.194 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-136.136.2 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-136.136.2~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1107.108 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1059.62 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1059.62~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1059.62.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1064.66 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1030.31 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1053.53 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1109.115 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1058.61 | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux-oracle | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1058.61~22.04.1 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1106.109 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1061.65 | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux-raspi | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux-realtime | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:25.10 | linux-riscv | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-136.136~22.04.3 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-vmware | 6.8.0-1008.8 | UBUNTU-CVE-2026-43405 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1033.34 | UBUNTU-CVE-2026-43405 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1075.79 | UBUNTU-CVE-2026-43405 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c – before ee5588e2bc41acb73f6676c0520420c107cd0140a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c – before 86f7060cd638d6eb042e8ed780fb83a59ca0dcb3a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c – before 5f2806684b05bd24d05c091083b8e2517ba8ffaca5cbd5fc22d5043a8a76e15d75d031fe24d1f69c – before b268984ae88cb0dcd7a8e8263962c748448e26e8a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c – before ba0a4df8c563536857dcbf7b4dbd0f2a15f57acea5cbd5fc22d5043a8a76e15d75d031fe24d1f69c – before 08bc6173fd611ad5a40f472bf5f15b92aea0fe40a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c – before 770444611f047dbfd4517ec0bc1b179d40c2f346 |
| Linux | Linux | 5.11 |
Weakness: CWE-190 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
- https://git.kernel.org/stable/c/ee5588e2bc41acb73f6676c0520420c107cd0140
- https://git.kernel.org/stable/c/86f7060cd638d6eb042e8ed780fb83a59ca0dcb3
- https://git.kernel.org/stable/c/5f2806684b05bd24d05c091083b8e2517ba8ffac
- https://git.kernel.org/stable/c/b268984ae88cb0dcd7a8e8263962c748448e26e8
- https://git.kernel.org/stable/c/ba0a4df8c563536857dcbf7b4dbd0f2a15f57ace
- https://git.kernel.org/stable/c/08bc6173fd611ad5a40f472bf5f15b92aea0fe40
- https://git.kernel.org/stable/c/770444611f047dbfd4517ec0bc1b179d40c2f346