CVE-2026-80557
Linux kernel vulnerability
- Published26 Aug 2026
Description
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/00ead17c7de137a692edee59f2772e6af687e8eb
- https://git.kernel.org/stable/c/1c824e7c75bb4adf19553dd4ea944a5d83096be8
- https://git.kernel.org/stable/c/7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1
- https://git.kernel.org/stable/c/85479b7d65b4ebcb07fbbe57230976793974ab4a
- https://git.kernel.org/stable/c/c59219a6b62d74936963983e5815524c3de8dd79
- https://git.kernel.org/stable/c/cb8246e5846dbbe34930903a90c7a90dd8e5910b
- https://git.kernel.org/stable/c/eab3eeb68bfc639d74f27256f05546af5c4f787d
- https://git.kernel.org/stable/c/f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6
Frequently asked
Is CVE-2026-80557 being actively exploited?
CVE-2026-80557 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.53%.
How severe is CVE-2026-80557?
CVE-2026-80557 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.53% probability of exploitation.
How do I fix CVE-2026-80557?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-80557 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.