CVE-2026-80557libceph: fix OOB read in decode_watchers() via missing bounds check
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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 ]
- CVSS
- 9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c before 85479b7d65b4ebcb07fbbe57230976793974ab4a; from a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c before 1c824e7c75bb4adf19553dd4ea944a5d83096be8; from a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c before f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6; from a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c before eab3eeb68bfc639d74f27256f05546af5c4f787d; from a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c before c59219a6b62d74936963983e5815524c3de8dd79; from a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c before cb8246e5846dbbe34930903a90c7a90dd8e5910b; from a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c before 7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1; from a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c before 00ead17c7de137a692edee59f2772e6af687e8eb | CNA record |
References
- https://git.kernel.org/stable/c/85479b7d65b4ebcb07fbbe57230976793974ab4a
- https://git.kernel.org/stable/c/1c824e7c75bb4adf19553dd4ea944a5d83096be8
- https://git.kernel.org/stable/c/f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6
- https://git.kernel.org/stable/c/eab3eeb68bfc639d74f27256f05546af5c4f787d
- https://git.kernel.org/stable/c/c59219a6b62d74936963983e5815524c3de8dd79
- https://git.kernel.org/stable/c/cb8246e5846dbbe34930903a90c7a90dd8e5910b
- https://git.kernel.org/stable/c/7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1
- https://git.kernel.org/stable/c/00ead17c7de137a692edee59f2772e6af687e8eb
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.