<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 07:53:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49086 — net: openvswitch: fix leak of nested actions</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49086</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: fix leak of nested actions&lt;/p&gt;
&lt;p&gt;While parsing user-provided actions, openvswitch module may dynamically
allocate memory and store pointers in the internal copy of the actions.
So this memory has to be freed while destroying the actions.&lt;/p&gt;
&lt;p&gt;Currently there are only two such actions: ct() and set().  However,
there are many actions that can hold nested lists of actions and
ovs_nla_free_flow_actions() just jumps over them leaking the memory.&lt;/p&gt;
&lt;p&gt;For example, removal of the flow with the following actions will lead
to a leak of the memory allocated by nf_ct_tmpl_alloc():&lt;/p&gt;
&lt;p&gt;actions:clone(ct(commit),0)&lt;/p&gt;
&lt;p&gt;Non-freed set() action may also leak the &amp;#39;dst&amp;#39; structure for the
tunnel info including device references.&lt;/p&gt;
&lt;p&gt;Under certain conditions with a high rate of flow rotation that may
cause significant memory leak problem (2MB per second in reporter&amp;#39;s
case).  The problem is also hard to mitigate, because the user doesn&amp;#39;t
have direct control over the datapath flows generated by OVS.&lt;/p&gt;
&lt;p&gt;Fix that by iterating over all the nested actions and freeing
everything that needs to be freed recursively.&lt;/p&gt;
&lt;p&gt;New build time assertion should protect us from this problem if new
actions will be added in the future.&lt;/p&gt;
&lt;p&gt;Unfortunately, openvswitch module doesn&amp;#39;t use NLA_F_NESTED, so all
attributes has to be explicitly checked.  sample() and clone() actions
are mixing extra attributes into the user-provided action list.  That
prevents some…&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: fix leak of nested actions&lt;/p&gt;
&lt;p&gt;While parsing user-provided actions, openvswitch module may dynamically
allocate memory and store pointers in the internal copy of the actions.
So this memory has to be freed while destroying the actions.&lt;/p&gt;
&lt;p&gt;Currently there are only two such actions: ct() and set().  However,
there are many actions that can hold nested lists of actions and
ovs_nla_free_flow_actions() just jumps over them leaking the memory.&lt;/p&gt;
&lt;p&gt;For example, removal of the flow with the following actions will lead
to a leak of the memory allocated by nf_ct_tmpl_alloc():&lt;/p&gt;
&lt;p&gt;actions:clone(ct(commit),0)&lt;/p&gt;
&lt;p&gt;Non-freed set() action may also leak the &amp;#39;dst&amp;#39; structure for the
tunnel info including device references.&lt;/p&gt;
&lt;p&gt;Under certain conditions with a high rate of flow rotation that may
cause significant memory leak problem (2MB per second in reporter&amp;#39;s
case).  The problem is also hard to mitigate, because the user doesn&amp;#39;t
have direct control over the datapath flows generated by OVS.&lt;/p&gt;
&lt;p&gt;Fix that by iterating over all the nested actions and freeing
everything that needs to be freed recursively.&lt;/p&gt;
&lt;p&gt;New build time assertion should protect us from this problem if new
actions will be added in the future.&lt;/p&gt;
&lt;p&gt;Unfortunately, openvswitch module doesn&amp;#39;t use NLA_F_NESTED, so all
attributes has to be explicitly checked.  sample() and clone() actions
are mixing extra attributes into the user-provided action list.  That
prevents some…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49086</guid>
    </item>
  </channel>
</rss>
