libceph: Use u32 for non-negative values in ceph_monmap_decode()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c · fixed in ee5588e2bc41acb73f6676c0520420c107cd0140; From a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c · fixed in 86f7060cd638d6eb042e8ed780fb83a59ca0dcb3; From a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c · fixed in 5f2806684b05bd24d05c091083b8e2517ba8ffac; From a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c · fixed in b268984ae88cb0dcd7a8e8263962c748448e26e8; From a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c · fixed in ba0a4df8c563536857dcbf7b4dbd0f2a15f57ace; From a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c · fixed in 08bc6173fd611ad5a40f472bf5f15b92aea0fe40; From a5cbd5fc22d5043a8a76e15d75d031fe24d1f69c · fixed in 770444611f047dbfd4517ec0bc1b179d40c2f346
- Linux Linux
5.11
- KernelLinux
From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.167; From 6.2.0 · fixed in 6.6.130; From 6.7.0 · fixed in 6.12.78; From 6.13.0 · fixed in 6.18.19; From 6.19.0 · fixed in 6.19.9
References 7
git.kernel.org
- stable/c/ee5588e2bc41acb73f6676c0520420c107cd0140
- stable/c/86f7060cd638d6eb042e8ed780fb83a59ca0dcb3
- stable/c/5f2806684b05bd24d05c091083b8e2517ba8ffac
- stable/c/b268984ae88cb0dcd7a8e8263962c748448e26e8
- stable/c/ba0a4df8c563536857dcbf7b4dbd0f2a15f57ace
- stable/c/08bc6173fd611ad5a40f472bf5f15b92aea0fe40
- stable/c/770444611f047dbfd4517ec0bc1b179d40c2f346