<?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>Tue, 06 Oct 2026 23:56:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-58071 — team: prevent adding a device which is already a team device lower</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-58071</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;team: prevent adding a device which is already a team device lower&lt;/p&gt;
&lt;p&gt;Prevent adding a device which is already a team device lower,
e.g. adding veth0 if vlan1 was already added and veth0 is a lower of
vlan1.&lt;/p&gt;
&lt;p&gt;This is not useful in practice and can lead to recursive locking:&lt;/p&gt;
&lt;p&gt;$ ip link add veth0 type veth peer name veth1
$ ip link set veth0 up
$ ip link set veth1 up
$ ip link add link veth0 name veth0.1 type vlan protocol 802.1Q id 1
$ ip link add team0 type team
$ ip link set veth0.1 down
$ ip link set veth0.1 master team0
team0: Port device veth0.1 added
$ ip link set veth0 down
$ ip link set veth0 master team0&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.13.0-rc2-virtme-00441-ga14a429069bb #46 Not tainted
--------------------------------------------
ip/7684 is trying to acquire lock:
ffff888016848e00 (team-&amp;gt;team_lock_key){+.+.}-{4:4}, at: team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973)&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
ffff888016848e00 (team-&amp;gt;team_lock_key){+.+.}-{4:4}, at: team_add_slave (drivers/net/team/team_core.c:1147 drivers/net/team/team_core.c:1977)&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
----
lock(team-&amp;gt;team_lock_key);
lock(team-&amp;gt;team_lock_key);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by ip/7684:&lt;/p&gt;
&lt;p&gt;s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;team: prevent adding a device which is already a team device lower&lt;/p&gt;
&lt;p&gt;Prevent adding a device which is already a team device lower,
e.g. adding veth0 if vlan1 was already added and veth0 is a lower of
vlan1.&lt;/p&gt;
&lt;p&gt;This is not useful in practice and can lead to recursive locking:&lt;/p&gt;
&lt;p&gt;$ ip link add veth0 type veth peer name veth1
$ ip link set veth0 up
$ ip link set veth1 up
$ ip link add link veth0 name veth0.1 type vlan protocol 802.1Q id 1
$ ip link add team0 type team
$ ip link set veth0.1 down
$ ip link set veth0.1 master team0
team0: Port device veth0.1 added
$ ip link set veth0 down
$ ip link set veth0 master team0&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.13.0-rc2-virtme-00441-ga14a429069bb #46 Not tainted
--------------------------------------------
ip/7684 is trying to acquire lock:
ffff888016848e00 (team-&amp;gt;team_lock_key){+.+.}-{4:4}, at: team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973)&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
ffff888016848e00 (team-&amp;gt;team_lock_key){+.+.}-{4:4}, at: team_add_slave (drivers/net/team/team_core.c:1147 drivers/net/team/team_core.c:1977)&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
----
lock(team-&amp;gt;team_lock_key);
lock(team-&amp;gt;team_lock_key);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by ip/7684:&lt;/p&gt;
&lt;p&gt;s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-58071</guid>
    </item>
  </channel>
</rss>
