<?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>Sun, 04 Oct 2026 16:16:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38470 — net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38470</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime&lt;/p&gt;
&lt;p&gt;Assuming the &amp;#34;rx-vlan-filter&amp;#34; feature is enabled on a net device, the
8021q module will automatically add or remove VLAN 0 when the net device
is put administratively up or down, respectively. There are a couple of
problems with the above scheme.&lt;/p&gt;
&lt;p&gt;The first problem is a memory leak that can happen if the &amp;#34;rx-vlan-filter&amp;#34;
feature is disabled while the device is running:&lt;/p&gt;
&lt;p&gt;# ip link add bond1 up type bond mode 0
 # ethtool -K bond1 rx-vlan-filter off
 # ip link del dev bond1&lt;/p&gt;
&lt;p&gt;When the device is put administratively down the &amp;#34;rx-vlan-filter&amp;#34;
feature is disabled, so the 8021q module will not remove VLAN 0 and the
memory will be leaked [1].&lt;/p&gt;
&lt;p&gt;Another problem that can happen is that the kernel can automatically
delete VLAN 0 when the device is put administratively down despite not
adding it when the device was put administratively up since during that
time the &amp;#34;rx-vlan-filter&amp;#34; feature was disabled. null-ptr-unref or
bug_on[2] will be triggered by unregister_vlan_dev() for refcount
imbalance if toggling filtering during runtime:&lt;/p&gt;
&lt;p&gt;$ ip link add bond0 type bond mode 0
$ ip link add link bond0 name vlan0 type vlan id 0 protocol 802.1q
$ ethtool -K bond0 rx-vlan-filter off
$ ifconfig bond0 up
$ ethtool -K bond0 rx-vlan-filter on
$ ifconfig bond0 down
$ ip link del vlan0&lt;/p&gt;
&lt;p&gt;Root cause is as below:
step1: add vlan0 for real_dev, such as bond, te…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime&lt;/p&gt;
&lt;p&gt;Assuming the &amp;#34;rx-vlan-filter&amp;#34; feature is enabled on a net device, the
8021q module will automatically add or remove VLAN 0 when the net device
is put administratively up or down, respectively. There are a couple of
problems with the above scheme.&lt;/p&gt;
&lt;p&gt;The first problem is a memory leak that can happen if the &amp;#34;rx-vlan-filter&amp;#34;
feature is disabled while the device is running:&lt;/p&gt;
&lt;p&gt;# ip link add bond1 up type bond mode 0
 # ethtool -K bond1 rx-vlan-filter off
 # ip link del dev bond1&lt;/p&gt;
&lt;p&gt;When the device is put administratively down the &amp;#34;rx-vlan-filter&amp;#34;
feature is disabled, so the 8021q module will not remove VLAN 0 and the
memory will be leaked [1].&lt;/p&gt;
&lt;p&gt;Another problem that can happen is that the kernel can automatically
delete VLAN 0 when the device is put administratively down despite not
adding it when the device was put administratively up since during that
time the &amp;#34;rx-vlan-filter&amp;#34; feature was disabled. null-ptr-unref or
bug_on[2] will be triggered by unregister_vlan_dev() for refcount
imbalance if toggling filtering during runtime:&lt;/p&gt;
&lt;p&gt;$ ip link add bond0 type bond mode 0
$ ip link add link bond0 name vlan0 type vlan id 0 protocol 802.1q
$ ethtool -K bond0 rx-vlan-filter off
$ ifconfig bond0 up
$ ethtool -K bond0 rx-vlan-filter on
$ ifconfig bond0 down
$ ip link del vlan0&lt;/p&gt;
&lt;p&gt;Root cause is as below:
step1: add vlan0 for real_dev, such as bond, te…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38470</guid>
    </item>
  </channel>
</rss>
