Quick answers
- Is CVE-2026-68082 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68082 being exploited in the wild.
- How severe is CVE-2026-68082?
- Critical severity, with a CVSS score of 9.8, published 8 August 2026.
- Which products and versions are affected?
- Linux Kernel <unknown>.
- Is there a fix for CVE-2026-68082?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-68082 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-68082?
- Check whether you run Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The decode_lockers() function in cls_lock_client.c contains two unsafe bare decode operations that lack bounds checking. First, ceph_decode_32(p) reads the num_lockers field without verifying the buffer has sufficient data, allowing an OSD to send struct_len=0 to advance the pointer past the validated boundary. Second, ceph_decode_8(p) after the decode loop can read one byte past the buffer if num_lockers is crafted to advance p exactly to the buffer end. Both operations read garbage values that are used directly in subsequent logic (kzalloc_objs and lock type discrimination). The fix replaces bare decode operations with safe variants (ceph_decode_32_safe and ceph_decode_8_safe) that perform proper bounds checking before reading. Attack requires the kernel client to issue lock.get_info class method, which is typical during RBD exclusive lock acquisition.
Affected products
- Linux Linux kernel <unknown>
Timeline
- 2026-08-08: disclosed