CVE-2026-106096
Medium 6.4No known exploitationFix status unknownCri-o: cri-o: writable linklogs bind mount allows pods to redirect privileged conmon log writes
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 5% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Weakness: CWE-59
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- Red Hat OpenShift's default restricted / restricted-v2 SCCs do not allow containers to run as UID 0. That blocks the tested attack, even though LinkLogs is allowed in CRI-O on 4.15 and later.SELinux is enforcing on OpenShift nodes and further limits which host files conmon can write. Do not disable SELinux. Until a fixed cri-o build is installed, customers should: 1. Keep default SCCs. Do not grant anyuid, privileged, or other SCCs that allow host UID 0 to untrusted projects. 2. Review existing grants. Find namespaces/SAs that can run as UID 0.
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Red Hat | Red Hat OpenShift Container Platform 4 | Not documented | Not documented | CVE Program |
| Red Hat | Red Hat OpenShift Container Platform 4 | Not documented | Not documented | CVE Program |
| Red Hat | Red Hat OpenShift Container Platform 5 | Not documented | Not documented | CVE Program |
| Red Hat | Red Hat OpenShift Container Platform 5 | Not documented | Not documented | CVE Program |
| Red Hat | Confidential Compute Attestation (status unknown) | Not documented | Not documented | CVE Program |
| Red Hat | Red Hat OpenShift Container Platform 4 (status unknown) | Not documented | Not documented | CVE Program |
| Red Hat | Red Hat OpenShift Container Platform 4 (status unknown) | Not documented | Not documented | CVE Program |
| Red Hat | Red Hat OpenShift Container Platform 4 (status unknown) | Not documented | Not documented | CVE Program |
| Red Hat | Red Hat OpenShift Container Platform 4 (status unknown) | Not documented | Not documented | CVE Program |
| Red Hat | Red Hat OpenShift Container Platform 5 (status unknown) | Not documented | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by redhat
Source: CVE Program (opens in a new tab)
Vendor guidance and references
- https://access.redhat.com/security/cve/CVE-2026-106096 (opens in a new tab)vdb-entry, x_refsource_redhat
- RHBZ#2546703 (opens in a new tab)issue-tracking, x_refsource_redhat