Creation of a very deep, nested directory structures inside a container leads to high inode usage, exhausting available system memory and triggering OOM killer. A malicious process inside a container can exploit this to cause a denial of service on the host system.
Additionally, CRI-O will fail to cleanup the malicious container as it's unable to remove the created deep directory. Both Go's stdlib and coreutils `rm` traverse the created directory structure during removal, increasing inode usage and causing system memory to spike, subsequently triggering OOM killer again.