GPU VulnDB

Database/Container, Kubernetes & orchestration

Podman containers-common seccomp profile: AF_VSOCK and NETLINK_AUDIT deny rules can be bypassed

CVSS 4.4CVE-2026-123876Container, Kubernetes & orchestrationcurated

Impact

The default seccomp profile that Podman applies through containers-common is supposed to stop containers from opening AF_VSOCK and NETLINK_AUDIT sockets. Those deny rules compare the socket arguments as full 64-bit values, but the kernel only reads the lower 32 bits. A process in the container can set the upper bits and open sockets the profile should block. On a shared GPU node or a VM-backed container host this weakens a default isolation layer: the container may reach host or hypervisor vsock services and the audit netlink interface. The record rates confidentiality and integrity impact as low and claims nothing beyond the bypass.

Who can reach it

Local: code already running inside a container that uses the default Podman seccomp profile, with low privileges (PR:L). No network access is needed.

What to do

Install the fixed containers-common package from your distribution (Red Hat erratum RHSA-2026:88737 covers RHEL 8/9/10 and OpenShift 4/5). A seccomp filter is set when a container starts, so containers that are already running keep the old profile until you recreate or restart them. If a workload cannot be restarted soon, a custom seccomp profile that compares the masked 32-bit argument is a stopgap.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.