CyberRota Analysis
AI-GeneratedThe vulnerability affects the Inspektor Gadget toolset used in Kubernetes clusters and Linux hosts, specifically in versions 0.27.0 to 0.53.1, where an unprivileged container can exploit the uprobe library resolver to consume excessive CPU resources. This can block the startup of other containers by leveraging a crafted /etc/ld.so.cache file, leading to degraded performance and delayed container initialization without impacting confidentiality or integrity. Organizations utilizing Inspektor Gadget in their Kubernetes or Docker environments should prioritize upgrading to version 0.53.1 to mitigate this issue.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Inspektor Gadget is a set of tools and framework for data collection and system inspection on Kubernetes clusters and Linux hosts using eBPF. From 0.27.0 until 0.53.1, the uprobe library resolver can allow an unprivileged container to consume excessive CPU and block other containers from starting by supplying a crafted /etc/ld.so.cache file while an uprobe-based gadget is active. The parser in pkg/uprobetracer/ldcache_parser.go trusts EntryCount enough to perform excessive iteration, computes cache1Len with overflowing uint32 arithmetic, and repeatedly calls readStringFromBytes in pkg/uprobetracer/bytes.go, where byte-by-byte immutable string concatenation produces quadratic work. While this processing occurs, pkg/container-hook holds the fanotify container-start pause, allowing a crafted cache to delay startup for roughly a minute, prevent Docker from starting other containers, and degrade monitoring. Processing caches from already-running containers can still consume CPU but does not hold the new-container startup pause, and the advisory establishes no confidentiality or integrity impact. This issue is fixed in version 0.53.1.