Linux kernel memory leak in Xen netfront fragment handling
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ad4f15dc2c70b1de5e0a64d27335962fbc9cf71c · < 086944c1c2cbb683543bc3ff08637847b03c8009| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's xen/netfront driver leaks an skb and its attached pages when a backend response chain has more slots than fit in the skb's fragments. A backend that sends such chains can cause repeated memory leaks. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with xen/netfront should check their versions; affected versions were not specified.