CVE-2026-24054: Kata Containers Runtime: Host block device can be hotplugged to the VM if the container image is malformed or contains no layers
Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. In versions prior to 3.26.0, when a container image is malformed or contains no layers, containerd falls back to bind-mounting an empty snapshotter directory for the container rootfs. When the Kata runtime attempts to mount the container rootfs, the bind mount causes the rootfs to be detected as a block device, leading to the underlying device being hotplugged to the guest. This can cause filesystem-level errors on the host due to double inode allocation, and may lead to the host's block device being mounted as read-only. Version 3.26.0 contains a patch for the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Kata Containers Runtimeto a version that resolves this vulnerability.Fixed in 3.26.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-24054?
The severity of CVE-2026-24054 is considered high due to the potential unauthorized access to the host's block devices.
How do I fix CVE-2026-24054?
To fix CVE-2026-24054, update the Kata Containers Runtime to version 3.26.0 or later.
What types of systems are affected by CVE-2026-24054?
CVE-2026-24054 affects systems running versions of Kata Containers Runtime prior to 3.26.0.
Does CVE-2026-24054 affect container security?
Yes, CVE-2026-24054 can compromise container security by allowing unauthorized access to the host block device.
What is the cause of CVE-2026-24054?
CVE-2026-24054 is caused by a malformed container image or one that contains no layers, allowing block devices to be hotplugged.