<?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://db.gcve.eu</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 16:19:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49234 — net: dsa: Avoid cross-chip syncing of VLAN filtering</title>
      <link>https://db.gcve.eu/vuln/cve-2022-49234</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: Avoid cross-chip syncing of VLAN filtering&lt;/p&gt;
&lt;p&gt;Changes to VLAN filtering are not applicable to cross-chip
notifications.&lt;/p&gt;
&lt;p&gt;On a system like this:&lt;/p&gt;
&lt;p&gt;.-----.   .-----.   .-----.
| sw1 +---+ sw2 +---+ sw3 |
&amp;#39;-1-2-&amp;#39;   &amp;#39;-1-2-&amp;#39;   &amp;#39;-1-2-&amp;#39;&lt;/p&gt;
&lt;p&gt;Before this change, upon sw1p1 leaving a bridge, a call to
dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.&lt;/p&gt;
&lt;p&gt;In this scenario:&lt;/p&gt;
&lt;p&gt;.---------.   .-----.   .-----.
|   sw1   +---+ sw2 +---+ sw3 |
&amp;#39;-1-2-3-4-&amp;#39;   &amp;#39;-1-2-&amp;#39;   &amp;#39;-1-2-&amp;#39;&lt;/p&gt;
&lt;p&gt;When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be
called for sw2 and sw3 with a non-existing port - leading to array
out-of-bounds accesses and crashes on mv88e6xxx.&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: Avoid cross-chip syncing of VLAN filtering&lt;/p&gt;
&lt;p&gt;Changes to VLAN filtering are not applicable to cross-chip
notifications.&lt;/p&gt;
&lt;p&gt;On a system like this:&lt;/p&gt;
&lt;p&gt;.-----.   .-----.   .-----.
| sw1 +---+ sw2 +---+ sw3 |
&amp;#39;-1-2-&amp;#39;   &amp;#39;-1-2-&amp;#39;   &amp;#39;-1-2-&amp;#39;&lt;/p&gt;
&lt;p&gt;Before this change, upon sw1p1 leaving a bridge, a call to
dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.&lt;/p&gt;
&lt;p&gt;In this scenario:&lt;/p&gt;
&lt;p&gt;.---------.   .-----.   .-----.
|   sw1   +---+ sw2 +---+ sw3 |
&amp;#39;-1-2-3-4-&amp;#39;   &amp;#39;-1-2-&amp;#39;   &amp;#39;-1-2-&amp;#39;&lt;/p&gt;
&lt;p&gt;When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be
called for sw2 and sw3 with a non-existing port - leading to array
out-of-bounds accesses and crashes on mv88e6xxx.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2022-49234</guid>
    </item>
  </channel>
</rss>
