PoC Monitor
← All CVEs
CVE-2026-18107published 28 Jul 2026 18:32 UTCData: JSON · API

Red Hat Enterprise Linux 10

Criu: criu: container escape via rseq critical section hijack during checkpoint/restore

A flaw was found in CRIU's handling of restartable sequences (rseq) during checkpoint/restore. A malicious process inside a container can register an rseq critical section that hijacks CRIU's parasite code injection during checkpoint, allowing it to spoof the process credentials saved in the checkpoint image. On restore, the container process gains elevated capabilities and zeroed UIDs/GIDs. The practical impact on Red Hat products is limited by several factors: checkpoint/restore requires root privileges (podman) or cluster-admin RBAC (OpenShift) to trigger and cannot be initiated from within the container itself; on OpenShift prior to 4.17 the feature required explicit opt-in, and on 4.17+ the kubelet checkpoint API RBAC is not configured by default; OpenShift enforces user namespaces by default for regular workloads (hostUsers is gated behind admin-only SCCs), which makes the spoofed capabilities namespace-scoped and ineffective for privilege escalation; SELinux type enforcement (container_t) blocks privilege transitions independently of capabilities; seccomp filters persist through checkpoint/restore and cannot be corrupted via the parasite; and kernel mount namespace ownership checks on RHEL 9/10 kernels prevent mount-based container escape even with spoofed capabilities.

First public PoC 61 daysafter publication · 27 Sep 2026
Public PoCs11 on GitHub
CVSS7.8high · scored by CNA · CWE-269
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Mitigation

The record names no fix. Check the vendor advisory below.

Workaround

Disable checkpoint/restore functionality in the container runtime if it is not required. If checkpoint/restore is needed, ensure containers run with user namespaces enabled, which limits the scope of spoofed capabilities to the user namespace.

References

Timeline

Days relative to CVE publication
t=0+14+28+42+56CVE published28 Jul 2026 · t = 0First public PoC27 Sep 2026 · t+61d

First public PoC 61 days after publication; not in CISA KEV. First PoC: robalb/criu-exploit (created 27 Sep 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
robalb/criu-exploit 27 Sep 2026 +61 d 3 PoC via PoC Index

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.