<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 08:44:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74478 — um: vector: fix use-after-free in vector_mmsg_rx()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74478</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: vector: fix use-after-free in vector_mmsg_rx()&lt;/p&gt;
&lt;p&gt;When vector_mmsg_rx() discards a packet whose overlay header fails
verify_header(), it frees the skb and continues the loop:&lt;/p&gt;
&lt;p&gt;if (header_check &amp;lt; 0) {
		dev_kfree_skb_irq(skb);
		vp-&amp;gt;estats.rx_encaps_errors++;
		continue;
	}&lt;/p&gt;
&lt;p&gt;The normal and short-packet paths fall through to the bottom of the
loop body, which clears the consumed slot and advances the cursors:&lt;/p&gt;
&lt;p&gt;(*skbuff_vector) = NULL;
	mmsg_vector++;
	skbuff_vector++;&lt;/p&gt;
&lt;p&gt;The verify_header() &amp;lt; 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.&lt;/p&gt;
&lt;p&gt;Discard the slot the same way the other paths do before continuing.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: vector: fix use-after-free in vector_mmsg_rx()&lt;/p&gt;
&lt;p&gt;When vector_mmsg_rx() discards a packet whose overlay header fails
verify_header(), it frees the skb and continues the loop:&lt;/p&gt;
&lt;p&gt;if (header_check &amp;lt; 0) {
		dev_kfree_skb_irq(skb);
		vp-&amp;gt;estats.rx_encaps_errors++;
		continue;
	}&lt;/p&gt;
&lt;p&gt;The normal and short-packet paths fall through to the bottom of the
loop body, which clears the consumed slot and advances the cursors:&lt;/p&gt;
&lt;p&gt;(*skbuff_vector) = NULL;
	mmsg_vector++;
	skbuff_vector++;&lt;/p&gt;
&lt;p&gt;The verify_header() &amp;lt; 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.&lt;/p&gt;
&lt;p&gt;Discard the slot the same way the other paths do before continuing.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74478</guid>
    </item>
  </channel>
</rss>
