Skip to main content

Linux Kernel CVE-2026-52955

| EUVDEUVD-2026-38823 CRITICAL
Incorrect Calculation of Buffer Size (CWE-131)
2026-06-24 Linux GHSA-jh5w-4gpm-r5xw
Critical
Disputed · 9.8 Vendor: Linux
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Attacker must control the Ceph cluster the victim trusts (AC:H), no victim privileges needed (PR:N); most reliable impact is kernel DoS (A:H) with possible limited memory disclosure/corruption (C:L/I:L).

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Red Hat
4.7 MEDIUM
qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jun 28, 2026 - 08:34 vuln.today
CVSS changed
Jun 28, 2026 - 08:22 NVD
9.8 (CRITICAL)
Patch available
Jun 24, 2026 - 18:02 EUVD
CVE Published
Jun 24, 2026 - 16:28 cve.org
CRITICAL 9.8
CVE Published
Jun 24, 2026 - 16:28 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

libceph: Fix potential out-of-bounds access in crush_decode()

A message of type CEPH_MSG_OSD_MAP containing a crush map with at least one bucket has two fields holding the bucket algorithm. If the values in these two fields differ, an out-of-bounds access can occur. This is the case because the first algorithm field (alg) is used to allocate the correct amount of memory for a bucket of this type, while the second algorithm field inside the bucket (b->alg) is used in the subsequent processing.

This patch fixes the issue by adding a check that compares alg and b->alg and aborts the processing in case they differ. Furthermore, b->alg is set to 0 in this case, because the destruction of the crush map also uses this field to determine the bucket type, which can again result in an out-of-bounds access when trying to free the memory pointed to by the fields of the bucket. To correctly free the memory allocated for the bucket in such a case, the corresponding call to kfree is moved from the algorithm-specific crush_destroy_bucket functions to the generic crush_destroy_bucket().

AnalysisAI

Out-of-bounds memory access in the Linux kernel's libceph CRUSH map decoder (crush_decode()) lets a malicious or compromised Ceph cluster corrupt kernel memory on a connecting client. A crafted CEPH_MSG_OSD_MAP message whose bucket carries mismatched algorithm fields (alg vs b->alg) causes memory to be allocated for one bucket type but processed and later freed as another, leading to OOB access during decode and again during crush map destruction. Despite a 9.8 CVSS, there is no public exploit identified at time of analysis and EPSS is low (0.18%, 8th percentile); the realistic attack surface is limited to hosts mounting/connecting to attacker-controlled Ceph (RBD/CephFS) infrastructure.

Technical ContextAI

libceph is the in-kernel client library used by the Ceph RBD block and CephFS filesystem drivers to talk to a Ceph storage cluster. CRUSH is Ceph's data-placement algorithm; the cluster distributes its topology to clients inside the OSD map as a serialized 'crush map' composed of buckets, each tagged with a placement algorithm (uniform, list, tree, straw, straw2). The root cause is a type-confusion-driven out-of-bounds access (effectively CWE-787/CWE-125, though the feed lists CWE as N/A and tags it 'Buffer Overflow'): crush_decode() reads one algorithm field (alg) to size the bucket allocation but a second, separately-decoded field (b->alg) to drive subsequent per-type processing. When the two disagree, code walks a structure larger than what was allocated. The destruction path (crush_destroy_bucket) compounds this by using b->alg to choose how to free, so a mismatched value also corrupts the free path. The fix rejects buckets where alg != b->alg, zeroes b->alg on that error, and centralizes the kfree() in the generic crush_destroy_bucket(). Per the CPE strings (cpe:2.3:a:linux:linux), this is upstream Linux kernel code affecting any build with CONFIG_CEPH_LIB.

RemediationAI

Apply your distribution's kernel update that includes this fix; the upstream patched versions are 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10, and mainline 7.1 (Vendor-released patch confirmed via the kernel.org stable commits, e.g. https://git.kernel.org/stable/c/6e70ef53e818c53eab28d7b0026b7fd03dddaba5). Choose the patched release matching your stable series and reboot, or use livepatch if your vendor ships one. Where immediate patching is not possible, the practical compensating control is to ensure kernel Ceph clients only connect to trusted clusters and to harden that trust boundary: enable Ceph cephx authentication and require-signatures (cephx_require_signatures / cephx_cluster_require_signatures) so clients reject spoofed monitor/OSD traffic, and use network segmentation or firewall rules to restrict the Ceph monitor/OSD ports (typically 6789/3300 for monitors and 6800-7300 for OSDs) to known cluster hosts only, blocking MITM injection of malicious OSD maps. If a host does not require kernel RBD/CephFS, unload the ceph/rbd/libceph modules (or avoid loading them) to remove the attack surface entirely; the trade-off is loss of in-kernel Ceph mounts, so this suits hosts that use userspace librbd/Ceph-FUSE or no Ceph at all. Validate fixes against https://nvd.nist.gov/vuln/detail/CVE-2026-52955.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.177 Container suse/sl-micro/6.1/base-os-container:2.2.1-5.155 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.206 Container suse/sl-micro/6.1/rt-os-container:2.2.1-5.152 Affected
Container suse/sle-micro-rancher/5.3:latest Container suse/sle-micro-rancher/5.4:5.4.4.5.149 Affected
Container suse/sle-micro/base-5.5:2.0.4-5.8.296 Affected
Container suse/sle-micro/kvm-5.5:2.0.4-3.5.570 Affected

Share

CVE-2026-52955 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy