Answer in brief
CVE-2026-53941 records a Medium severity vulnerability in Inspektor Gadget Uprobe gadgets: unprivileged container's ld.so.cache causes high CPU utilization and container startup DoS. The current sources do not mark it as known exploited. The current feed maps inspektor-gadget/inspektor-gadget (generic), github.com/inspektor-gadget/inspektor-gadget (go), github.com/inspektor-gadget/inspektor-gadget (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps inspektor-gadget/inspektor-gadget (generic), github.com/inspektor-gadget/inspektor-gadget (go), github.com/inspektor-gadget/inspektor-gadget (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| inspektor-gadget/inspektor-gadgetgeneric | >= 0.27.0, < 0.53.1 | Not reported |
| github.com/inspektor-gadget/inspektor-gadgetgo | >=0.27.0 <0.53.1 | 0.53.1 |
| github.com/inspektor-gadget/inspektor-gadgetgo | >=0.27.0,<0.53.1 | 0.53.1 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.