libceph: fix OOB read in decode_watchers() via missing bounds check
- 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.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, and 2 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: total
Summary
In the Linux kernel, the following vulnerability has been resolved: libceph: fix OOB read in decode_watchers() via missing bounds check ceph_start_decoding() validates that struct_len bytes remain in the buffer after the encoding header, but accepts struct_len=0 as valid: ceph_decode_need(p, end, 0, bad) always passes. When a malicious or compromised OSD sends an obj_list_watch_response_t reply with struct_len=0, ceph_start_decoding() returns success with p == end, leaving zero bytes guaranteed for subsequent reads. The immediately following ceph_decode_32(p) in decode_watchers() has no preceding bounds check. With p == end this is a 4-byte read past the validated buffer boundary. The garbage value is then passed directly to kzalloc_objs() as the watcher count. The sibling function decode_watcher() already uses the safe variants (ceph_decode_copy_safe, ceph_decode_64_safe, ceph_decode_skip_32) after its own ceph_start_decoding() call. decode_watchers() is the only site that uses the bare variant, confirming an oversight. Fix by replacing ceph_decode_32(p) with ceph_decode_32_safe(p, end, *num_watchers, bad), consistent with the established pattern. Attacker model: a malicious or compromised OSD in a multi-tenant Ceph deployment (e.g. cloud) can trigger this against any kernel client that calls CEPH_OSD_OP_LIST_WATCHERS, without any further privileges beyond OSD session establishment. [ idryomov: trim changelog ]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c · fixed in 85479b7d65b4ebcb07fbbe57230976793974ab4a; From a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c · fixed in 1c824e7c75bb4adf19553dd4ea944a5d83096be8; From a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c · fixed in f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6; From a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c · fixed in eab3eeb68bfc639d74f27256f05546af5c4f787d; From a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c · fixed in c59219a6b62d74936963983e5815524c3de8dd79; From a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c · fixed in cb8246e5846dbbe34930903a90c7a90dd8e5910b; From a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c · fixed in 7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1; From a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c · fixed in 00ead17c7de137a692edee59f2772e6af687e8eb
- Linux Linux
4.9
- KernelLinux
From 4.9.0 · fixed in 5.10.267; From 5.11.0 · fixed in 5.15.218; From 5.16.0 · fixed in 6.1.185; From 6.2.0 · fixed in 6.6.154; From 6.7.0 · fixed in 6.12.106; From 6.13.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.10
References 8
git.kernel.org
- stable/c/85479b7d65b4ebcb07fbbe57230976793974ab4a
- stable/c/1c824e7c75bb4adf19553dd4ea944a5d83096be8
- stable/c/f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6
- stable/c/eab3eeb68bfc639d74f27256f05546af5c4f787d
- stable/c/c59219a6b62d74936963983e5815524c3de8dd79
- stable/c/cb8246e5846dbbe34930903a90c7a90dd8e5910b
- stable/c/7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1
- stable/c/00ead17c7de137a692edee59f2772e6af687e8eb