GPU VulnDB

Database/Container, Kubernetes & orchestration

CRI-O: LinkLogs log mount stays writable, letting a container append data to host files

CVSS 6.4CVE-2026-106096Container, Kubernetes & orchestrationcurated

Impact

When the optional LinkLogs feature is on, CRI-O bind-mounts the host pod log directory into a pod emptyDir. The mount is meant to be read-only, but Linux ignores MS_RDONLY on the first bind, so it stays writable. A container running as UID 0 without privileges can plant a symlink at a future kubelet log path. The privileged conmon process then appends log data the attacker controls to an existing host file. Red Hat describes this as an append-only host integrity issue, not general remote code execution. On a shared GPU cluster, the realistic risk is a tenant corrupting or adding to host files on the node. LinkLogs is off by default.

Who can reach it

A tenant who can run a non-privileged container as UID 0 on a node where CRI-O has LinkLogs enabled. Needs the ability to schedule a pod; no host access.

What to do

Check whether LinkLogs is enabled in your CRI-O configuration. If it is not, you are not exposed. If it is, apply the fixed CRI-O or OpenShift packages from the Red Hat advisory (the record does not give a version), then restart CRI-O on each node, which in practice means draining it first. Until then, disable LinkLogs or stop pods from running as UID 0.

References

Related entries

All Container, Kubernetes & orchestration 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.