PoC Monitor
← All CVEs
CVE-2026-80561published 26 Aug 2026 14:37 UTCData: JSON · API

Linux

libceph: fix multiple unsafe decodes in decode_locker()

In the Linux kernel, the following vulnerability has been resolved: libceph: fix multiple unsafe decodes in decode_locker() decode_locker() in cls_lock_client.c contains three unsafe decode operations that allow a malicious or compromised OSD to trigger slab-out-of-bounds reads: 1. ceph_decode_copy() at the locker_id_t name field has no preceding bounds check. With p == end after ceph_start_decoding() accepts struct_len=0, this reads sizeof(ceph_entity_name) = 9 bytes past the validated buffer boundary. 2. *p += sizeof(struct ceph_timespec) after the locker_info_t header is an unchecked pointer advance. A malicious OSD can position p past end, causing all subsequent _safe checks to pass against a bogus boundary. 3. len = ceph_decode_32(p) has no preceding bounds check, and the immediately following *p += len is uncapped. A malicious OSD can send len=0xffffffff, advancing p gigabytes past end and escaping the decode window entirely. Fix all three by replacing bare operations with their safe variants: ceph_decode_copy -> ceph_decode_copy_safe *p += sizeof(...) -> ceph_decode_skip_n ceph_decode_32(p) -> ceph_decode_32_safe *p += len -> ceph_decode_skip_n A new label is added to return -EINVAL on any bounds violation. -EINVAL is appropriate here: the data received from the OSD is structurally malformed, which is an invalid argument to the decode contract regardless of whether the caller or the wire is at fault. Attacker model: a malicious or compromised OSD in a multi-tenant Ceph deployment can trigger this against any kernel client that issues the lock.get_info class method (e.g. during RBD exclusive lock acquisition) without any further privileges beyond OSD session establishment. [ idryomov: use ceph_decode_skip_string() to skip description, trim changelog ]

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.8critical · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= d4ed4a530562881cc5225050e42d96034f405aae, < 1ed45c8d96498725eb54f740172f9068d8673906
  • >= d4ed4a530562881cc5225050e42d96034f405aae, < 6265103e78f0ee7e2518de9cf938b94bee9700a0
  • >= d4ed4a530562881cc5225050e42d96034f405aae, < 3c3716dc06a34e4ca7f743f5fcfa07fbc5a11070
  • >= d4ed4a530562881cc5225050e42d96034f405aae, < fa4aa86fff0c56799c2e3f51a88879053285f4a9
  • >= d4ed4a530562881cc5225050e42d96034f405aae, < dbfd83f722a78446ec18a476ef7a38e52240b50a
  • >= d4ed4a530562881cc5225050e42d96034f405aae, < d1bba38574d095f191557d397d9633f08cd966b1
  • >= d4ed4a530562881cc5225050e42d96034f405aae, < 51c8d238fe7236de627ab1a1433694552a904136
  • >= d4ed4a530562881cc5225050e42d96034f405aae, < 437b6551cfcc235eea1d735a874f9d421f555e17

Fixed in 1ed45c8d96498725eb54f740172f9068d8673906, 6265103e78f0ee7e2518de9cf938b94bee9700a0, 3c3716dc06a34e4ca7f743f5fcfa07fbc5a11070, fa4aa86fff0c56799c2e3f51a88879053285f4a9, dbfd83f722a78446ec18a476ef7a38e52240b50a, d1bba38574d095f191557d397d9633f08cd966b1, 51c8d238fe7236de627ab1a1433694552a904136, 437b6551cfcc235eea1d735a874f9d421f555e17

Linux Linux
  • 4.9

Fixed in 0, 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10, 7.2

Mitigation

Upgrade Linux to 1ed45c8d96498725eb54f740172f9068d8673906 or 6265103e78f0ee7e2518de9cf938b94bee9700a0 or 3c3716dc06a34e4ca7f743f5fcfa07fbc5a11070 or fa4aa86fff0c56799c2e3f51a88879053285f4a9 or dbfd83f722a78446ec18a476ef7a38e52240b50a or d1bba38574d095f191557d397d9633f08cd966b1 or 51c8d238fe7236de627ab1a1433694552a904136 or 437b6551cfcc235eea1d735a874f9d421f555e17 or later.

Upgrade Linux to 0 or 5.10.266 or 5.15.217 or 6.1.184 or 6.6.153 or 6.12.105 or 6.18.46 or 7.1.10 or 7.2 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published26 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.