<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T23:57:12.182613+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2024-58071</id>
    <title>CVE-2024-58071 — team: prevent adding a device which is already a team device lower</title>
    <updated>2026-10-06T23:57:12.184420+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>team: prevent adding a device which is already a team device lower</p>
<p>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.</p>
<p>This is not useful in practice and can lead to recursive locking:</p>
<p>$ 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</p>
<p>============================================
WARNING: possible recursive locking detected
6.13.0-rc2-virtme-00441-ga14a429069bb #46 Not tainted
--------------------------------------------
ip/7684 is trying to acquire lock:
ffff888016848e00 (team-&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)</p>
<p>but task is already holding lock:
ffff888016848e00 (team-&gt;team_lock_key){+.+.}-{4:4}, at: team_add_slave (drivers/net/team/team_core.c:1147 drivers/net/team/team_core.c:1977)</p>
<p>other info that might help us debug this:
Possible unsafe locking scenario:</p>
<p>CPU0
----
lock(team-&gt;team_lock_key);
lock(team-&gt;team_lock_key);</p>
<p>*** DEADLOCK ***</p>
<p>May be due to missing lock nesting notation</p>
<p>2 locks held by ip/7684:</p>
<p>s…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-58071"/>
  </entry>
</feed>
