Linux Kernel: Deadlock (CVE-2024-58071)
Published Last modified Sources: Siemens ProductCERT, Debian LTS, SUSE, BSI, CVE.org, EUVD, Msrc Update Guide
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: team: prevent adding a device which is already a team device lower 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. This is not useful in practice and can lead to recursive locking: $ 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 ============================================ WARNING: possible recursive locking detected 6.13.0-rc2-virtme-00441-ga14a429069bb #46 Not tainted -------------------------------------------- ip/7684 is trying to acquire lock: ffff888016848e00 (team->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) but task is already holding lock: ffff888016848e00 (team->team_lock_key){+.+.}-{4:4}, at: team_add_slave (drivers/net/team/team_core.c:1147 drivers/net/team/team_core.c:1977) other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(team->team_lock_key); lock(team->team_lock_key); *** DEADLOCK *** May be due to missing lock nesting notation 2 locks held by ip/7684: stack backtrace: CPU: 3 UID: 0 PID: 7684 Comm: ip Not tainted 6.13.0-rc2-virtme-00441-ga14a429069bb #46 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:122) print_deadlock_bug.cold (kernel/locking/lockdep.c:3040) __lock_acquire (kernel/locking/lockdep.c:3893 kernel/locking/lockdep.c:5226) ? netlink_broadcast_filtered (net/netlink/af_netlink.c:1548) lock_acquire.part.0 (kernel/locking/lockdep.c:467 kernel/locking/lockdep.c:5851) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? trace_lock_acquire (./include/trace/events/lock.h:24 (discriminator 2)) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? lock_acquire (kernel/locking/lockdep.c:5822) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) __mutex_lock (kernel/locking/mutex.c:587 kernel/locking/mutex.c:735) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? fib_sync_up (net/ipv4/fib_semantics.c:2167) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) notifier_call_chain (kernel/notifier.c:85) call_netdevice_notifiers_info (net/core/dev.c:1996) __dev_notify_flags (net/core/dev.c:8993) ? __dev_change_flags (net/core/dev.c:8975) dev_change_flags (net/core/dev.c:9027) vlan_device_event (net/8021q/vlan.c:85 net/8021q/vlan.c:470) ? br_device_event (net/bridge/br.c:143) notifier_call_chain (kernel/notifier.c:85) call_netdevice_notifiers_info (net/core/dev.c:1996) dev_open (net/core/dev.c:1519 net/core/dev.c:1505) team_add_slave (drivers/net/team/team_core.c:1219 drivers/net/team/team_core.c:1977) ? __pfx_team_add_slave (drivers/net/team/team_core.c:1972) do_set_master (net/core/rtnetlink.c:2917) do_setlink.isra.0 (net/core/rtnetlink.c:3117)
Update Linux Kernel to version 5.4.291, Linux Kernel to version 5.10.235, Linux Kernel to version 5.15.179.
- Affected
- Linux Kernel
lt 3.3..5.4.291 - Linux Kernel
lt 5.5..5.10.235 - Linux Kernel
lt 5.11..5.15.179 - Linux Kernel
lt 5.16..6.1.129 - Linux Kernel
lt 6.2..6.6.76 - Linux Kernel
lt 6.7..6.12.13 - Linux Kernel
lt 6.13..6.13.2
- Linux Kernel
- Fixed in
- Linux Kernel
5.4.291 - Linux Kernel
5.10.235 - Linux Kernel
5.15.179 - Linux Kernel
6.1.129 - Linux Kernel
6.6.76 - Linux Kernel
6.12.13 - Linux Kernel
6.13.2 - Linux Kernel
6.14
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
5.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
5.5
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: Siemens ProductCERT, Debian LTS, SUSE, BSI, CVE.org, EUVD, Msrc Update Guide
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 7.3
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 36.02 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 5.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 5.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 7.3
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 1 October 2025
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-667
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: team: prevent adding a device which is already a team device lower 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. This is not useful in practice and can lead to recursive locking: $ 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 ============================================ WARNING: possible recursive locking detected 6.13.0-rc2-virtme-00441-ga14a429069bb #46 Not tainted -------------------------------------------- ip/7684 is trying to acquire lock: ffff888016848e00 (team->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) but task is already holding lock: ffff888016848e00 (team->team_lock_key){+.+.}-{4:4}, at: team_add_slave (drivers/net/team/team_core.c:1147 drivers/net/team/team_core.c:1977) other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(team->team_lock_key); lock(team->team_lock_key); *** DEADLOCK *** May be due to missing lock nesting notation 2 locks held by ip/7684: stack backtrace: CPU: 3 UID: 0 PID: 7684 Comm: ip Not tainted 6.13.0-rc2-virtme-00441-ga14a429069bb #46 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:122) print_deadlock_bug.cold (kernel/locking/lockdep.c:3040) __lock_acquire (kernel/locking/lockdep.c:3893 kernel/locking/lockdep.c:5226) ? netlink_broadcast_filtered (net/netlink/af_netlink.c:1548) lock_acquire.part.0 (kernel/locking/lockdep.c:467 kernel/locking/lockdep.c:5851) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? trace_lock_acquire (./include/trace/events/lock.h:24 (discriminator 2)) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? lock_acquire (kernel/locking/lockdep.c:5822) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) __mutex_lock (kernel/locking/mutex.c:587 kernel/locking/mutex.c:735) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? fib_sync_up (net/ipv4/fib_semantics.c:2167) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) notifier_call_chain (kernel/notifier.c:85) call_netdevice_notifiers_info (net/core/dev.c:1996) __dev_notify_flags (net/core/dev.c:8993) ? __dev_change_flags (net/core/dev.c:8975) dev_change_flags (net/core/dev.c:9027) vlan_device_event (net/8021q/vlan.c:85 net/8021q/vlan.c:470) ? br_device_event (net/bridge/br.c:143) notifier_call_chain (kernel/notifier.c:85) call_netdevice_notifiers_info (net/core/dev.c:1996) dev_open (net/core/dev.c:1519 net/core/dev.c:1505) team_add_slave (drivers/net/team/team_core.c:1219 drivers/net/team/team_core.c:1977) ? __pfx_team_add_slave (drivers/net/team/team_core.c:1972) do_set_master (net/core/rtnetlink.c:2917) do_setlink.isra.0 (net/core/rtnetlink.c:3117)
Source: siemens_advisory, Debian LTS Advisories, suse_csaf, BSI WID Portal, BSI CSAF, cvelistv5, ENISA EUVD, NVD (NIST), Microsoft Security Update Guide, CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Siemens | SIMATIC S7 |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bullseye |
| Linux | debian | linux-6.1 | bullseye |
| Linux | linux | linux_kernel | — |
Weakness classes (CWE)
CWE-667Improper Locking
Class
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Entry at MITRE CWE-667
References & sources
- git.kernel.orgstable/c/0a7794b9ca78c8e7d001c583bf05736169de3f20
- git.kernel.orgstable/c/62ff1615815d565448c37cb8a7a2a076492ec471
- git.kernel.orgstable/c/bd099a2fa9be983ba0e90a57a59484fe9d520ba8
- git.kernel.orgstable/c/adff6ac889e16d97abd1e4543f533221127e978a
- git.kernel.orgstable/c/184a564e6000b41582f160a5be9a9b5aabe22ac1
- git.kernel.orgstable/c/1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c
- git.kernel.orgstable/c/d9bce1310c0e2a55888e3e08c9f69d8377b3a377
- git.kernel.orgstable/c/3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50
- lists.debian.orgdebian-lts-announce/2025/05/msg00030.html
- lists.debian.orgdebian-lts-announce/2025/03/msg00028.html
- Siemens ProductCERTproductcert/html/ssa-265688.html
- Siemens ProductCERTproductcert/html/ssa-784472.html
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedLinux
New references:- https://git.kernel.org/stable/c/0a7794b9ca78c8e7d001c583bf05736169de3f20
- https://git.kernel.org/stable/c/184a564e6000b41582f160a5be9a9b5aabe22ac1
- https://git.kernel.org/stable/c/1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c
- https://git.kernel.org/stable/c/3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50
and 4 more references
Show 24 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://git.kernel.org/stable/c/0a7794b9ca78c8e7d001c583bf05736169de3f20Reference added —https://git.kernel.org/stable/c/184a564e6000b41582f160a5be9a9b5aabe22ac1Reference added —https://git.kernel.org/stable/c/1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6cReference added —https://git.kernel.org/stable/c/3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50Reference added —https://git.kernel.org/stable/c/62ff1615815d565448c37cb8a7a2a076492ec471Reference added —https://git.kernel.org/stable/c/adff6ac889e16d97abd1e4543f533221127e978aReference added —https://git.kernel.org/stable/c/bd099a2fa9be983ba0e90a57a59484fe9d520ba8Reference added —https://git.kernel.org/stable/c/d9bce1310c0e2a55888e3e08c9f69d8377b3a377Reference removed https://git.kernel.org/stable/c/0a7794b9ca78c8e7d001c583bf05736169de3f20—Reference removed https://git.kernel.org/stable/c/184a564e6000b41582f160a5be9a9b5aabe22ac1—Reference removed https://git.kernel.org/stable/c/1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c—Reference removed https://git.kernel.org/stable/c/3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50—Reference removed https://git.kernel.org/stable/c/62ff1615815d565448c37cb8a7a2a076492ec471—Reference removed https://git.kernel.org/stable/c/adff6ac889e16d97abd1e4543f533221127e978a—Reference removed https://git.kernel.org/stable/c/bd099a2fa9be983ba0e90a57a59484fe9d520ba8—Reference removed https://git.kernel.org/stable/c/d9bce1310c0e2a55888e3e08c9f69d8377b3a377—Reference type removed https://git.kernel.org/stable/c/0a7794b9ca78c8e7d001c583bf05736169de3f20 Types: Patch—Reference type removed https://git.kernel.org/stable/c/184a564e6000b41582f160a5be9a9b5aabe22ac1 Types: Patch—Reference type removed https://git.kernel.org/stable/c/1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c Types: Patch—Reference type removed https://git.kernel.org/stable/c/3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50 Types: Patch—Reference type removed https://git.kernel.org/stable/c/62ff1615815d565448c37cb8a7a2a076492ec471 Types: Patch—Reference type removed https://git.kernel.org/stable/c/adff6ac889e16d97abd1e4543f533221127e978a Types: Patch—Reference type removed https://git.kernel.org/stable/c/bd099a2fa9be983ba0e90a57a59484fe9d520ba8 Types: Patch—Reference type removed https://git.kernel.org/stable/c/d9bce1310c0e2a55888e3e08c9f69d8377b3a377 Types: Patch—Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedCVE Program
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://lists.debian.org/debian-lts-announce/2025/03/msg00028.htmlReference added —https://lists.debian.org/debian-lts-announce/2025/05/msg00030.htmlReference removed https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html—Reference removed https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html—Source identifier: af854a3a-2127-422b-91ae-364da2661108
Record modifiedSiemens ADP
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2024/58xxx/CVE-2024-58071.json">CVE-2024-58071</a>Reference added —https://cert-portal.siemens.com/productcert/html/ssa-265688.htmlReference added —https://cert-portal.siemens.com/productcert/html/ssa-784472.htmlReference removed https://cert-portal.siemens.com/productcert/html/ssa-265688.html—Source identifier: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2024-58071"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-58071.svg?lang=en" alt="CVE-2024-58071 – NEOSEC Intel" height="20"></a>