<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T11:52:05.663792+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2022-50063</id>
    <title>CVE-2022-50063 — net: dsa: felix: suppress non-changes to the tagging protocol</title>
    <updated>2026-10-07T11:52:05.680696+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: dsa: felix: suppress non-changes to the tagging protocol</p>
<p>The way in which dsa_tree_change_tag_proto() works is that when
dsa_tree_notify() fails, it doesn'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-&gt;ops-&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).</p>
<p>This means for the felix driver that if we report an error in
felix_change_tag_protocol(), we'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-&gt;teardown,
which (if it manages to run at all, after walking through corrupted data
structures) will leave the ports inoperational anyway.</p>
<p>The bug can be readily reproduced if we force an error while in
tag_8021q mode; this crashes the kernel.</p>
<p>echo ocelot-8021q &gt; /sys/class/net/eno2/dsa/tagging
echo edsa &gt; /sys/class/net/eno2/dsa/tagging # -EPROTONOSUPPORT</p>
<p>Unable to handle kernel NULL pointer dereference at virtual address 0000000000000014
Call trace:
 vcap_entry_get+0x24/0x124
 ocelot_vcap_filter_del+0x…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2022-50063"/>
  </entry>
</feed>
