CVE-2026-68082

published 8 Aug 2026 · updated 14 Nov 2026

libceph: fix two unsafe bare decodes in decode_lockers()

9.8CriticalCVSS 9.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c8ade01170a27d8ede0d761c255268af81e417f8, Kernel 001835c599899ef1bd3506a815110a6374451554, Kernel 02430f6f729b297e803d0605871f0a670b4eafd6 and 12 more.

In the Linux kernel, the following vulnerability has been resolved: libceph: fix two unsafe bare decodes in decode_lockers() decode_lockers() in cls_lock_client.c contains two bare decode operations that allow a malicious or compromised OSD to trigger slab-out-of-bounds reads: 1. ceph_decode_32(p) at the num_lockers field has no preceding bounds check. ceph_start_decoding() accepts struct_len=0 as valid -- the internal ceph_decode_need(p, end, 0, bad) always passes -- so when an OSD sends struct_len=0, ceph_start_decoding() returns success with p == end. The immediately following bare ceph_decode_32(p) then reads 4 bytes past the validated buffer boundary. The garbage value is passed directly to kzalloc_objs() as the locker count. The sibling function decode_watchers() in osd_client.c already uses ceph_decode_32_safe() after its own ceph_start_decoding() call. decode_lockers() was the only site using the bare variant. 2. ceph_decode_8(p) after the decode_locker() loop has no preceding bounds check. If an OSD crafts num_lockers such that the loop advances p exactly to end, the subsequent bare ceph_decode_8(p) reads one byte past the validated buffer boundary. The result is passed directly into *type, which is used as a lock type discriminator by callers, giving an OSD-controlled one-byte OOB read with direct influence over the lock type field. Fix both by replacing bare operations with their safe variants: ceph_decode_32(p) -> ceph_decode_32_safe(p, end, *num_lockers, err_inval) ceph_decode_8(p) -> ceph_decode_8_safe(p, end, *type, err_free_lockers) The goto targets differ intentionally: err_inval: is a new label returning -EINVAL directly. It is used for the pre-allocation failure path where *lockers is not yet allocated and must not be passed to ceph_free_lockers(). err_free_lockers: is the existing label. It is used for the post-allocation failure path where *lockers is allocated and must be freed. ret is set to -EINVAL before ceph_decode_8_safe() so that err_free_lockers returns the correct error code on bounds violation. Without this, err_free_lockers would return a stale ret value (0 from the successful decode_locker() loop), silently swallowing the error. -EINVAL is correct for both failure paths. The data received from the OSD is structurally malformed. -ENOMEM would misrepresent the failure class to callers and to stable@ backporters triaging error paths. 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). [ idryomov: trim changelog, formatting ]

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=d4ed4a530562881cc5225050e42d96034f405aae <c8ade01170a27d8ede0d761c255268af81e417f8, >=d4ed4a530562881cc5225050e42d96034f405aae <001835c599899ef1bd3506a815110a6374451554, >=d4ed4a530562881cc5225050e42d96034f405aae <02430f6f729b297e803d0605871f0a670b4eafd6, >=d4ed4a530562881cc5225050e42d96034f405aae <57ba829804fe6d34bbac3b826c4b15c1caa54862, >=d4ed4a530562881cc5225050e42d96034f405aae <7c422364acd93d7da1dfc27d6b54635a269653a1, >=d4ed4a530562881cc5225050e42d96034f405aae <89df5d71f83f8e2781286798fd8ae5e42cf5f1a7, >=d4ed4a530562881cc5225050e42d96034f405aae <a109a556115271ca7896dcda7b4b7e45e156c227, >=d4ed4a530562881cc5225050e42d96034f405aae <a54be593d0b749161b08a1e56189b2cb9114267a, =4.9c8ade01170a27d8ede0d761c255268af81e417f8, 001835c599899ef1bd3506a815110a6374451554, 02430f6f729b297e803d0605871f0a670b4eafd6, 57ba829804fe6d34bbac3b826c4b15c1caa54862, 7c422364acd93d7da1dfc27d6b54635a269653a1, 89df5d71f83f8e2781286798fd8ae5e42cf5f1a7, a109a556115271ca7896dcda7b4b7e45e156c227, a54be593d0b749161b08a1e56189b2cb9114267a
linux-kernel: Kernel>=5.11.0 <5.15.217, >=5.16.0 <6.1.184, >=6.13.0 <6.18.46, >=6.19.0 <7.1.6, >=6.2.0 <6.6.153, >=6.7.0 <6.12.105, >=4.9.0 <5.10.2665.15.217, 6.1.184, 6.18.46, 7.1.6, 6.6.153, 6.12.105, 5.10.266

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-68082 severity on Zeptric[![CVE-2026-68082](https://zeptric.io/badge/cve/CVE-2026-68082.svg)](https://zeptric.io/cve/CVE-2026-68082)