CVE-2024-58071: team: prevent adding a device which is already a team device lower
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0a7794b9ca78c8e7d001c583bf05736169de3f20, 184a564e6000b41582f160a5be9a9b5aabe22ac1, 1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1; cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.0 5.15.180.1-1.
Low priority for now. Upgrade to Linux Linux 0a7794b9ca78c8e7d001c583bf05736169de3f20, 184a564e6000b41582f160a5be9a9b5aabe22ac1, 1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1; cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.0 5.15.180.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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)
- Published
- Mar 6, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 5.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.3 and later · before 5.4.291
- linux linux kernel5.5 and later · before 5.10.235
- linux linux kernel5.11 and later · before 5.15.179
- linux linux kernel5.16 and later · before 6.1.129
- linux linux kernel6.2 and later · before 6.6.76
- linux linux kernel6.7 and later · before 6.12.13
- linux linux kernel6.13 and later · before 6.13.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.3affected
- 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 and later · before 0a7794b9ca78c8e7d001c583bf05736169de3f20affected · git
- 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 and later · before 62ff1615815d565448c37cb8a7a2a076492ec471affected · git
- 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 and later · before bd099a2fa9be983ba0e90a57a59484fe9d520ba8affected · git
- 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 and later · before adff6ac889e16d97abd1e4543f533221127e978aaffected · git
- 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 and later · before 184a564e6000b41582f160a5be9a9b5aabe22ac1affected · git
- 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 and later · before 1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6caffected · git
- 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 and later · before d9bce1310c0e2a55888e3e08c9f69d8377b3a377affected · git
- 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 and later · before 3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50affected · git
- before 3.3not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.129-1 | 6.1.129-1 |
| Debian:13 | linux | before 6.12.13-1 | 6.12.13-1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0-RT_Update_7 | before 1-1.3 | 1-1.3 |
| SUSE:Linux Micro 6.0 | kernel-rt | before 6.4.0-30.1 | 6.4.0-30.1 |
| SUSE:Linux Micro 6.0 | kernel-source-rt | before 6.4.0-30.1 | 6.4.0-30.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-58063Mar 6, 2025 · wifi: rtlwifi: fix memory leaks and invalid access at probe error path22Monitor
- ← EarlierCVE-2024-58068Mar 6, 2025 · OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized22Monitor
- Later →CVE-2024-58072Mar 6, 2025 · wifi: rtlwifi: remove unused check_buddy_priv31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0a7794b9ca78c8e7d001c583bf05736169de3f20 | Vendor (CNA) |
| Linux Linux | 184a564e6000b41582f160a5be9a9b5aabe22ac1 | Vendor (CNA) |
| Linux Linux | 1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c | Vendor (CNA) |
| Linux Linux | 3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50 | Vendor (CNA) |
| Linux Linux | 62ff1615815d565448c37cb8a7a2a076492ec471 | Vendor (CNA) |
| Linux Linux | adff6ac889e16d97abd1e4543f533221127e978a | Vendor (CNA) |
| Linux Linux | bd099a2fa9be983ba0e90a57a59484fe9d520ba8 | Vendor (CNA) |
| Linux Linux | d9bce1310c0e2a55888e3e08c9f69d8377b3a377 | Vendor (CNA) |
| cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.129-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_7 | 1-1.3 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-30.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-30.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (11 more)Show less
- git.kernel.org/stable/c/184a564e6000b41582f160a5be9a9b5aabe22ac1
- git.kernel.org/stable/c/1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c
- git.kernel.org/stable/c/3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50
- git.kernel.org/stable/c/62ff1615815d565448c37cb8a7a2a076492ec471
- git.kernel.org/stable/c/adff6ac889e16d97abd1e4543f533221127e978a
- git.kernel.org/stable/c/bd099a2fa9be983ba0e90a57a59484fe9d520ba8
- git.kernel.org/stable/c/d9bce1310c0e2a55888e3e08c9f69d8377b3a377
- lists.debian.org/debian-lts-announce/2025/03/msg00028.html
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.