A flaw in the Linux kernel’s virtio transport zero‑copy path causes the pinned‑page accounting function to use a zero count after the iterator has been consumed, so RLIMIT_MEMLOCK enforcement is skipped for the final skb. An attacker can therefore allocate more pinned memory than permitted, potentially enabling memory exhaustion or a denial of service. The weakness is an improper resource‑management error that bypasses kernel limits.

All Linux kernel versions that do not include the commit that patches virtio_transport_init_zcopy_skb. The specific kernel releases affected are not listed in the CVE data, so any kernel prior to the fix is potentially vulnerable.

The vulnerability does not provide a publicly documented active exploit, and its EPSS score is not available. Because it bypasses a system resource limit, its risk is moderate to high in environments where privileged or untrusted guests can rely on vsock/virtio zero‑copy messaging. The attack vector is inferred to be local or confined to the virtual machine ecosystem; no public data indicates an external network exploit.