um: vector: fix use-after-free in vector_mmsg_rx()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb · < 180ff4c81faf01ec4e06082c9daa7c40518ead89| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
um: vector: fix use-after-free in vector_mmsg_rx()
When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop:
if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; }
The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors:
(*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++;
The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path.
Discard the slot the same way the other paths do before continuing.
From the CVE record · Linux
The Linux kernel's vector_mmsg_rx() can reuse a freed packet buffer after rejecting an invalid overlay header, causing a refcount underflow and use-after-free. Any peer on an affected GRE or L2TPv3 transport can trigger this with a cookie or session-ID mismatch, without authentication.
Engineers running Linux kernels with UML vector networking over GRE or L2TPv3 should check whether their kernel is affected; no affected versions were provided.