Bug 2546703 (CVE-2026-106096)

Summary: CVE-2026-106096 cri-o: cri-o: Writable LinkLogs bind mount allows pods to redirect privileged conmon log writes
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: akhatavk, aos-team-art-private, asdas, dpaolell, jdelft, jupierce, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, security-response-team, sghai, sidsharm, suppawar, vlaad
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
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 MS_RDONLY on the initial bind and the CRI mount stays writable. A non-privileged UID 0 container can place a symlink at a future kubelet log path so that privileged conmon later appends attacker-controlled log data to an existing host file. This is an append-only host integrity issue, not universal remote code execution; LinkLogs is not enabled by default.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-10-06 17:25:00 UTC
Optional LinkLogs (link-logs.crio.io) bind-mounts /var/log/pods into an emptyDir with MS_BIND|MS_RDONLY and no remount, so the workload still gets a writable view. A UID 0, non-privileged pod can symlink the next kubelet attempt log path to an existing host file. CRI-O keeps valid symlinks; conmon, started from the privileged CRI-O service, opens that path for append without O_NOFOLLOW and writes the payload. Requires the annotation on the runtime handler allowlist, pod create, and effective UID 0 (baseline allows this; restricted / typical OpenShift SCC often do not). SELinux may block some targets. Code since v1.26.4 / v1.27.1 / v1.28.0; default handlers that do not allow the annotation are not reachable. Workaround: do not allow link-logs.crio.io; fix by forcing the workload emptyDir OCI mounts read-only while leaving CRI-O's host-side log linking writable.