CVE-2026-24054: Kata Containers: improper handling of empty rootfs triggers host block device hotplug
CVE-2026-24054 affects Kata Containers versions prior to 3.26.0. When a container image is malformed or has no layers, containerd can bind-mount an empty snapshotter directory as the container rootfs, which the Kata runtime may treat as a block device and hotplug into the guest. The record describes possible host filesystem errors and a read-only host block device; NVD rates it critical (CVSS 3.1 score 10), and version 3.26.0 contains a patch.
Overview
Kata Containers is an open source project that implements lightweight virtual machines that behave like containers. According to the GitHub Security Advisory, when a container image is malformed or has no layers, containerd can fall back to bind-mounting an empty snapshotter directory as the container root filesystem. The Kata runtime may then detect that mount as a block device and hotplug the underlying device into the guest.
Impact
The advisory states that this can cause filesystem-level errors on the host due to double inode allocation, and may lead to the host block device being mounted read-only. The record maps the weakness to CWE-754, Improper Check for Unusual or Exceptional Conditions. The NVD vector indicates no confidentiality impact and high integrity and availability impact, with scope changed.
Affected products and versions
- Kata Containers versions prior to 3.26.0, as listed in the record as less than 3.26.0.
- Version 3.26.0 is stated to contain a patch for the issue.
- The record lists patch references in containerd's overlay snapshotter code, but does not state which containerd versions are affected or fixed.
Exploitation status
The record shows KEV listing as false, and no confirmed exploitation appears in the sources consulted. One reference is tagged as Exploit in the record, but the record does not describe any exploitation in the wild. EPSS and SSVC data are not present in the record.
Remediation and mitigation
- Upgrade Kata Containers to version 3.26.0 or later, as stated by the advisory.
- Review the containerd version in use and consult the containerd overlay code reference and the fix commit when planning updates.
- Until patched, limit workloads to trusted images and validate that images contain expected layers before deployment.
Detection guidance
- Monitor Kata guests for unexpected block device hotplug events tied to container rootfs mounts.
- Watch host logs for filesystem errors or unexpected read-only remounts of block devices.
- Add checks in image pipelines that flag images with no layers or malformed manifests.
Limitations of the available information
The record does not provide the exact containerd versions affected or fixed, nor the reproduction conditions in detail. The CVSS scores differ between providers: NVD lists 3.1 score 10, while GitHub as CNA lists 4.0 score 8.8. No EPSS or SSVC data is available, so likelihood of exploitation is unknown.
Frequently asked questions
Which Kata Containers versions are affected by CVE-2026-24054?
The record states that versions prior to 3.26.0 are affected. Version 3.26.0 is stated to contain a patch for the issue.
Is this vulnerability known to be exploited in the wild?
The record shows KEV listing as false, and no confirmed exploitation appears in the sources consulted. The record does not describe in-the-wild activity.
What should administrators do now?
Upgrade Kata Containers to version 3.26.0 or later, review containerd versions in use, and restrict workloads to trusted images with expected layers until patched.
This analysis was drafted with AI assistance from verified source data and automatically checked against it.