llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · github.com/containerd/containerd/v2

GHSA-5P7C-HGGF-C748

containerd CRI plugin: mount and snapshot leak when container checkpoint restore fails

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche el mismo día de la divulgación
Exposición37 dDesde la divulgación, 13 oct 2026, 5:48 p. m.
Detección35 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche v2.3.7
Monitoreo
Detectada +1
13 oct 26
18 nov 26
20 nov 26
13 oct 26
23 oct 26
1 nov 26
11 nov 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-5P7C-HGGF-C748 divulgada
Divulgación Modificada Última actualización del registro
Remediación Parche v2.3.7 github.com/containerd/containerd/v2 · 0 d desde divulgación
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Impact

A bug in containerd's CRI plugin on Linux can cause containerd to leak read-only mounts and pinned snapshots when restoring a container from a checkpoint image fails. Repeatedly creating containers from a checkpoint image with malformed metadata or a base image that cannot be pulled can exhaust the host mount table and disk space indefinitely. In Kubernetes, this resource exhaustion can prevent containerd and the kubelet from pulling images or starting new pods on the node.

Patches

This bug has been fixed in containerd 2.3.7 and 2.2.10. Users should update to these versions to resolve the issue. To release resources from mounts leaked prior to the update, administrators must unmount any lingering `/tmp/checkpoint*` mount points on the host (or reboot the node) so containerd can garbage-collect the pinned snapshots.

Workarounds

containerd 2.4 does not support restore via the CRI plugin and is not vulnerable to this bug.

In containerd 2.3 and 2.2, disable CRI checkpoint and restore support by setting `enable_criu = false` under `[plugins."io.containerd.cri.v1.runtime"]` (or `[plugins."io.containerd.grpc.v1.cri"]` in config version 2) in containerd's configuration, or ensure `enable_experimental_restore_via_create` is set to `false` (the default starting in containerd 2.3.4 and 2.2.7). Restrict pod image references to trusted registries (for example, using a Kubernetes `ValidatingAdmissionPolicy` or admission webhook).

Credits

The containerd project would like to thank @IamwhatIamSY for responsibly disclosing this issue in accordance with the containerd security policy https://github.com/containerd/project/blob/main/SECURITY.md.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in containerd https://github.com/containerd/containerd/issues/new/choose
  • Email us at [security@containerd.io](mailto:security@containerd.io)

To report a security issue in containerd:
* Report a new vulnerability https://github.com/containerd/containerd/security/advisories/new
* Email us at [security@containerd.io](mailto:security@containerd.io)

Versiones

Rangos afectados

Afectada Corregida Última
github.com/containerd/containerd/v2≥ 2.3.0 < 2.3.7
2.3.0
2.3.7
v2.4.2
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/containerd/containerd/v2
Corregida v2.3.7 0 d v2.4.2 no afectada
Versiones corregidas2.3.7v2.3.7
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/containerd/containerd/security/advisories/GHSA-5p7c-hggf-c748

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.