External risk intelligence

Linux Kernel libceph Invalid OSD Index Out-of-Bounds Access.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-80558

This vulnerability exists within the Linux kernel's Ceph client implementation, which handles internal storage cluster communication. These processes occur deep within the infrastructure layer and are not exposed to the public internet. Access is restricted to internal, peer-to-peer communication between storage cluster nodes.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in the Linux kernel's Ceph storage component, which could allow unauthorized access to data integrity and availability if exploited. The issue stems from how the kernel handles specific storage indices, potentially leading to out-of-bounds memory access when processing corrupted data. The main concern is confirming relevance and exposure within your specific environment.

  • Kernel flaw could expose data integrity and availability.
  • Remember for potential, though unlikely, internal storage impact.
  • Confirm relevance and exposure in your Linux storage systems.

Attack Path

How an attacker could exploit the issue

An attacker could leverage a corrupted Ceph configuration, specifically an invalid OSD map, to trigger a vulnerability in the Linux kernel. This corrupted map could contain invalid indices that are not properly validated by the kernel's Ceph client. When processing this map, the kernel may use these invalid indices to access memory outside of its intended boundaries, potentially leading to severe system compromise.

  • Requires access to a corrupted Ceph map.
  • Triggered by processing invalid OSD indices.
  • Leads to out-of-bounds memory access.

Live Threat

Current exploitation, exposure, and threat context

A corrupted Ceph map could cause the Linux kernel to access memory outside its intended boundaries. This may occur when the kernel processes specific parts of a Ceph map, specifically `primary_temp`.

  • Kernel memory access outside bounds.
  • Corrupted Ceph map data is processed.
  • Potential system instability or crashes.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability resides in the Linux kernel's libceph component, impacting how Ceph monitors and OSDs handle OSD indices. Responsibility for addressing this likely falls to the infrastructure or platform teams managing the Ceph storage cluster, in coordination with security teams. The immediate first step is to identify all instances of the affected Linux kernel component within the storage infrastructure, assess their exposure and criticality, and then plan remediation based on that assessment.

  • Infrastructure or platform teams own resolution.
  • Verify Ceph OSD index handling and exposure.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Linux kernel's libceph component?

Libceph is the library within the Linux kernel that enables communication between the operating system and Ceph storage clusters. It manages the underlying networking and data distribution logic required for high-performance, distributed storage systems. When servers act as clients to access or manage these clusters, they rely on this component to process cluster maps and track the status of Object Storage Devices (OSDs) that hold the data.

What is the vulnerability in CVE-2026-80558?

This is an out-of-bounds memory access vulnerability. It occurs when the Linux kernel fails to validate certain storage indices provided in a Ceph map. If these indices point to values outside the allowed range, the kernel attempts to read from memory locations it should not access. This weakness can lead to system instability, crashes, or potential interference with data integrity and service availability within the storage environment.

How is this vulnerability triggered?

The flaw is triggered when the kernel receives and processes a corrupted Ceph OSD map. Specifically, it involves an unchecked index within the 'primary_temp' field of that map. The issue does not occur when receiving well-formed, valid map data; the kernel must process maliciously crafted or corrupted data that includes indices higher than the defined maximum OSD limit or below the specified minimum to initiate the improper memory access.

Is my storage system at risk according to Halo Surface Signal?

According to Halo Surface Signal, this vulnerability is very unlikely to be accessible from the public internet. The libceph component functions deep within the infrastructure layer, facilitating internal peer-to-peer communication between storage cluster nodes. Because this process is restricted to internal network traffic between these nodes, it is not typically exposed to external attackers.

How should I respond to CVE-2026-80558?

Infrastructure and platform teams should begin by identifying all Linux systems in their environment that utilize libceph for cluster management. Once identified, evaluate the specific storage configurations to determine if they are currently processing untrusted map data. Work with your security team to prioritize patching these kernel components, ensuring that your storage infrastructure remains resilient against potential memory-related faults.

References