Bug 2546703 (CVE-2026-106096) - CVE-2026-106096 cri-o: cri-o: Writable LinkLogs bind mount allows pods to redirect privileged conmon log writes
Summary: CVE-2026-106096 cri-o: cri-o: Writable LinkLogs bind mount allows pods to red...
Keywords:
Status: NEW
Alias: CVE-2026-106096
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-06 17:25 UTC by OSIDB Bzimport
Modified: 2026-11-17 13:49 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.