<?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>Mon, 28 Sep 2026 06:36:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74664 — net: openvswitch: reallocate update replies for mismatched IDs</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74664</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;net: openvswitch: reallocate update replies for mismatched IDs&lt;/p&gt;
&lt;p&gt;ovs_flow_cmd_new() preallocates the optional reply skb before it takes
ovs_mutex and before it knows which existing flow will be updated.&lt;/p&gt;
&lt;p&gt;That is normally fine because the skb is sized from the request flow
identifier.  That identifier also becomes the inserted flow&amp;#39;s identifier.
For updates, however, a request with a UFID may miss the UFID lookup and
then fall back to the flow key lookup.  That lookup can legitimately find
an existing key-identified flow.  UFIDs are optional and the flow key is
the primary identifier.&lt;/p&gt;
&lt;p&gt;For echoed replies, ovs_flow_cmd_fill_info() writes the matched flow&amp;#39;s
identifier, not the request identifier used for the preallocation.  A short
request UFID can therefore leave too little room for the key identifier.
The fill can then fail with -EMSGSIZE and hit the BUG_ON(error &amp;lt; 0) in the
update path.&lt;/p&gt;
&lt;p&gt;Once the update target has been resolved, reallocate the reply skb if the
matched flow needs a larger reply than the request identifier allowed.  Do
this before replacing the actions so the request can still fail cleanly if
the rare extra allocation fails.&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;net: openvswitch: reallocate update replies for mismatched IDs&lt;/p&gt;
&lt;p&gt;ovs_flow_cmd_new() preallocates the optional reply skb before it takes
ovs_mutex and before it knows which existing flow will be updated.&lt;/p&gt;
&lt;p&gt;That is normally fine because the skb is sized from the request flow
identifier.  That identifier also becomes the inserted flow&amp;#39;s identifier.
For updates, however, a request with a UFID may miss the UFID lookup and
then fall back to the flow key lookup.  That lookup can legitimately find
an existing key-identified flow.  UFIDs are optional and the flow key is
the primary identifier.&lt;/p&gt;
&lt;p&gt;For echoed replies, ovs_flow_cmd_fill_info() writes the matched flow&amp;#39;s
identifier, not the request identifier used for the preallocation.  A short
request UFID can therefore leave too little room for the key identifier.
The fill can then fail with -EMSGSIZE and hit the BUG_ON(error &amp;lt; 0) in the
update path.&lt;/p&gt;
&lt;p&gt;Once the update target has been resolved, reallocate the reply skb if the
matched flow needs a larger reply than the request identifier allowed.  Do
this before replacing the actions so the request can still fail cleanly if
the rare extra allocation fails.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74664</guid>
    </item>
  </channel>
</rss>
