GPU VulnDB

Database/Control plane, storage & DevOps

Inspektor Gadget: crafted ld.so.cache in a container stalls the container-start hook cluster-wide

CVSS 6.9CVE-2026-53941Control plane, storage & DevOpscurated

Impact

While an uprobe-based gadget is active, Inspektor Gadget parses /etc/ld.so.cache from container images to resolve libraries. The parser trusts the header EntryCount, computes a length with overflowing uint32 arithmetic, and builds strings byte by byte, so a crafted cache file turns into quadratic work. The damaging part is where that work happens: pkg/container-hook holds the fanotify container-start pause for the duration, so one unprivileged tenant container can delay container startup by roughly a minute, stop Docker from starting other containers on that node, and blind monitoring while it does. On a GPU node that is a scheduling stall affecting every other tenant on the box, not just the attacker. The advisory establishes availability impact only - no confidentiality or integrity claim.

Who can reach it

Any tenant who can run an unprivileged container with an image they control on a node where Inspektor Gadget is running an uprobe-based gadget. No elevated container privileges are required. A cache file processed from an already-running container still burns CPU but does not hold the start pause.

What to do

Upgrade Inspektor Gadget to 0.53.1 (affected from 0.27.0). This is a DaemonSet image bump and pod restart on each node - no node drain or reboot. As an interim mitigation, stop running uprobe-based gadgets on nodes that host untrusted tenant workloads.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.