Overlaybd
Monthly
Integer overflow in containerd overlaybd's LSMT index loader (do_load_index) lets a crafted, untrusted overlaybd blob pulled from a registry corrupt heap state and crash the host-side runtime, degrading availability for all overlaybd-backed containers on the node. Affected are overlaybd builds through 1.0.18 that are actually used as the container snapshotter/backend; exploitation is unauthenticated (CVSS PR:N) but requires high attack complexity (AC:H) - the victim must load an attacker-controlled blob in a deployment running multiple overlaybd-backed containers, which is why Scope is Changed. Impact is availability-only (C:N/I:N/A:H, CVSS 6.8); there is no public exploit identified at time of analysis and no CISA KEV confirmation, and organizations pulling only from trusted, signed sources are not realistically exposed.
Integer overflow in containerd overlaybd's LSMT index loader (do_load_index) lets a crafted, untrusted overlaybd blob pulled from a registry corrupt heap state and crash the host-side runtime, degrading availability for all overlaybd-backed containers on the node. Affected are overlaybd builds through 1.0.18 that are actually used as the container snapshotter/backend; exploitation is unauthenticated (CVSS PR:N) but requires high attack complexity (AC:H) - the victim must load an attacker-controlled blob in a deployment running multiple overlaybd-backed containers, which is why Scope is Changed. Impact is availability-only (C:N/I:N/A:H, CVSS 6.8); there is no public exploit identified at time of analysis and no CISA KEV confirmation, and organizations pulling only from trusted, signed sources are not realistically exposed.