Live › vulnerability › CVE-2026-99057
Go to dashboardIn the Linux kernel's Xen network frontend (netfront), a receive path that fails to fit a response chain into an skb leaks that skb and its attached pages. The backend controls how many slots it sends, so each overflowing chain leaks memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Linux guests running as Xen paravirtualized domains that use the netfront network driver are the systems to look at. The sources do not say which kernel versions are affected or whether the flaw is reachable from outside the host. Systems not running Linux on Xen, such as bare metal or KVM guests, are not affected.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
xen/netfront: don't leak the skb when xennet_fill_frags() fails
When a response chain has more slots than fit in the skb's frags, xennet_fill_frags() returns an error and xennet_poll() jumps to its error path. That path moves what's left on tmpq to errq to be freed, but the skb being filled was already dequeued from tmpq, so it's never freed. Each chain that overflows leaks the skb and the pages attached to it as frags, and the backend decides how many slots it sends.
Put the skb back on tmpq before taking the error path, like the xennet_set_skb_gso() failure just above it does.
This page as .md · .json · in your agent: get_signal("CVE-2026-99057")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.