Linux
um: vector: fix use-after-free in vector_mmsg_rx()
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. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb, < 967c779c9853d2a1cc9cd8e61d300250c348f3d9
- >= 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb, < a7bc015bb798c525e7a82dd14225c6aeb994274b
- >= 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb, < 7dc9781e320d664c9bdd50003c9acfddf363d1e1
- >= 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb, < 4b9601595e8b6b5d18878cac0aeabc687d241111
- >= 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb, < 67d58ab4f2ccf7145f3da07e025735a09c79de1b
- >= 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb, < 180ff4c81faf01ec4e06082c9daa7c40518ead89
- >= 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb, < 804b681002ead233abf49a3efd681f5468a835f9
- >= 49da7e64f33e80edffb1a9eeb230fa4c3f42dffb, < af421e9aed3920c7ac88c24daa48606c7112feca
Fixed in 967c779c9853d2a1cc9cd8e61d300250c348f3d9, a7bc015bb798c525e7a82dd14225c6aeb994274b, 7dc9781e320d664c9bdd50003c9acfddf363d1e1, 4b9601595e8b6b5d18878cac0aeabc687d241111, 67d58ab4f2ccf7145f3da07e025735a09c79de1b, 180ff4c81faf01ec4e06082c9daa7c40518ead89, 804b681002ead233abf49a3efd681f5468a835f9, af421e9aed3920c7ac88c24daa48606c7112feca
- 4.17
Fixed in 0, 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2
Mitigation
Upgrade Linux to 967c779c9853d2a1cc9cd8e61d300250c348f3d9 or a7bc015bb798c525e7a82dd14225c6aeb994274b or 7dc9781e320d664c9bdd50003c9acfddf363d1e1 or 4b9601595e8b6b5d18878cac0aeabc687d241111 or 67d58ab4f2ccf7145f3da07e025735a09c79de1b or 180ff4c81faf01ec4e06082c9daa7c40518ead89 or 804b681002ead233abf49a3efd681f5468a835f9 or af421e9aed3920c7ac88c24daa48606c7112feca or later.
Upgrade Linux to 0 or 5.10.265 or 5.15.216 or 6.1.183 or 6.6.151 or 6.12.103 or 6.18.44 or 7.1.8 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.