5 matches found
CVE-2026-106096
A flaw was found in CRI-O. When the optional Linux LinkLogs feature is enabled, the host pod log directory is bind-mounted into a pod emptyDir and is intended to be read-only, but Linux ignores MSRDONLY on the initial bind and the CRI mount stays writable. A non-privileged UID 0 container can pla...
CVE-2026-106096
A flaw was found in CRI-O. When the optional Linux LinkLogs feature is enabled, the host pod log directory is bind-mounted into a pod emptyDir and is intended to be read-only, but Linux ignores MSRDONLY on the initial bind and the CRI mount stays writable. A non-privileged UID 0 container can pla...
CVE-2026-106096
A flaw in CRI-O allows for an append-only host integrity issue when the optional Linux LinkLogs feature is enabled. Because Linux ignores MS_RDONLY on the initial bind, the host pod log directory remains writable within a pod emptyDir mount. A non-privileged UID 0 container can exploit this by pl...
EUVD-2026-128410
A flaw was found in CRI-O. When the optional Linux LinkLogs feature is enabled, the host pod log directory is bind-mounted into a pod emptyDir and is intended to be read-only, but Linux ignores MSRDONLY on the initial bind and the CRI mount stays writable. A non-privileged UID 0 container can pla...
CVE-2026-106096 Cri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes
A flaw was found in CRI-O. When the optional Linux LinkLogs feature is enabled, the host pod log directory is bind-mounted into a pod emptyDir and is intended to be read-only, but Linux ignores MSRDONLY on the initial bind and the CRI mount stays writable. A non-privileged UID 0 container can pla...