Linux
libceph: fix OOB read in decode_watchers() via missing bounds check
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 ]
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, < 85479b7d65b4ebcb07fbbe57230976793974ab4a
- >= a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, < 1c824e7c75bb4adf19553dd4ea944a5d83096be8
- >= a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, < f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6
- >= a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, < eab3eeb68bfc639d74f27256f05546af5c4f787d
- >= a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, < c59219a6b62d74936963983e5815524c3de8dd79
- >= a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, < cb8246e5846dbbe34930903a90c7a90dd8e5910b
- >= a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, < 7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1
- >= a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, < 00ead17c7de137a692edee59f2772e6af687e8eb
Fixed in 85479b7d65b4ebcb07fbbe57230976793974ab4a, 1c824e7c75bb4adf19553dd4ea944a5d83096be8, f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6, eab3eeb68bfc639d74f27256f05546af5c4f787d, c59219a6b62d74936963983e5815524c3de8dd79, cb8246e5846dbbe34930903a90c7a90dd8e5910b, 7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1, 00ead17c7de137a692edee59f2772e6af687e8eb
- 4.9
Fixed in 0, 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, 6.18.47, 7.1.10, 7.2
Mitigation
Upgrade Linux to 85479b7d65b4ebcb07fbbe57230976793974ab4a or 1c824e7c75bb4adf19553dd4ea944a5d83096be8 or f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6 or eab3eeb68bfc639d74f27256f05546af5c4f787d or c59219a6b62d74936963983e5815524c3de8dd79 or cb8246e5846dbbe34930903a90c7a90dd8e5910b or 7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1 or 00ead17c7de137a692edee59f2772e6af687e8eb or later.
Upgrade Linux to 0 or 5.10.267 or 5.15.218 or 6.1.185 or 6.6.154 or 6.12.106 or 6.18.47 or 7.1.10 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.