<?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 17:27:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50063 — net: dsa: felix: suppress non-changes to the tagging protocol</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-50063</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: dsa: felix: suppress non-changes to the tagging protocol&lt;/p&gt;
&lt;p&gt;The way in which dsa_tree_change_tag_proto() works is that when
dsa_tree_notify() fails, it doesn&amp;#39;t know whether the operation failed
mid way in a multi-switch tree, or it failed for a single-switch tree.
So even though drivers need to fail cleanly in
ds-&amp;gt;ops-&amp;gt;change_tag_protocol(), DSA will still call dsa_tree_notify()
again, to restore the old tag protocol for potential switches in the
tree where the change did succeeed (before failing for others).&lt;/p&gt;
&lt;p&gt;This means for the felix driver that if we report an error in
felix_change_tag_protocol(), we&amp;#39;ll get another call where proto_ops ==
old_proto_ops. If we proceed to act upon that, we may do unexpected
things. For example, we will call dsa_tag_8021q_register() twice in a
row, without any dsa_tag_8021q_unregister() in between. Then we will
actually call dsa_tag_8021q_unregister() via old_proto_ops-&amp;gt;teardown,
which (if it manages to run at all, after walking through corrupted data
structures) will leave the ports inoperational anyway.&lt;/p&gt;
&lt;p&gt;The bug can be readily reproduced if we force an error while in
tag_8021q mode; this crashes the kernel.&lt;/p&gt;
&lt;p&gt;echo ocelot-8021q &amp;gt; /sys/class/net/eno2/dsa/tagging
echo edsa &amp;gt; /sys/class/net/eno2/dsa/tagging # -EPROTONOSUPPORT&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000014
Call trace:
 vcap_entry_get+0x24/0x124
 ocelot_vcap_filter_del+0x…&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: dsa: felix: suppress non-changes to the tagging protocol&lt;/p&gt;
&lt;p&gt;The way in which dsa_tree_change_tag_proto() works is that when
dsa_tree_notify() fails, it doesn&amp;#39;t know whether the operation failed
mid way in a multi-switch tree, or it failed for a single-switch tree.
So even though drivers need to fail cleanly in
ds-&amp;gt;ops-&amp;gt;change_tag_protocol(), DSA will still call dsa_tree_notify()
again, to restore the old tag protocol for potential switches in the
tree where the change did succeeed (before failing for others).&lt;/p&gt;
&lt;p&gt;This means for the felix driver that if we report an error in
felix_change_tag_protocol(), we&amp;#39;ll get another call where proto_ops ==
old_proto_ops. If we proceed to act upon that, we may do unexpected
things. For example, we will call dsa_tag_8021q_register() twice in a
row, without any dsa_tag_8021q_unregister() in between. Then we will
actually call dsa_tag_8021q_unregister() via old_proto_ops-&amp;gt;teardown,
which (if it manages to run at all, after walking through corrupted data
structures) will leave the ports inoperational anyway.&lt;/p&gt;
&lt;p&gt;The bug can be readily reproduced if we force an error while in
tag_8021q mode; this crashes the kernel.&lt;/p&gt;
&lt;p&gt;echo ocelot-8021q &amp;gt; /sys/class/net/eno2/dsa/tagging
echo edsa &amp;gt; /sys/class/net/eno2/dsa/tagging # -EPROTONOSUPPORT&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000014
Call trace:
 vcap_entry_get+0x24/0x124
 ocelot_vcap_filter_del+0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-50063</guid>
    </item>
  </channel>
</rss>
