BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2024-58071High confidence

team: prevent adding a device which is already a team device lower

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 12 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

23 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 19 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.129-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2024-58071 · CSAF 2.0 · revision 58 · interimSUSE Product Security TeamCVE-2024-58071
325 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
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: 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)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-265688 · CSAF 2.0 · revision 13 · interimSiemens ProductCERTSSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Summary
team: prevent adding a device which is already a team device lower
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-54029

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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)

What

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)

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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)

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-667
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0499Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Auswirkungen zu erzeugen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250312Security Bulletin 12 Mar 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Mar 2025, published on 12 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-58055 Référence CVE CVE-2024-58056 https://www.cve.org/CVERecord?id=CVE-2024-58056 Référence CVE CVE-2024-58057 https://www.cve.org/CVERecord?id=CVE-2024-58057 Référence CVE CVE-2024-58058 https://www.cve.org/CVERecord?id=CVE-2024-58058 Référence CVE CVE-2024-58061 https://www.cve.org/CVERecord?id=CVE-2024-58061 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58068 https://www.cve.org/CVERecord?id=CVE-2024-58068 Référence CVE CVE-2024-58069 https://www.cve.org/CVERecord?id=CVE-2024-58069 Référence CVE CVE-2024-58070 https://www.cve.org/CVERecord?id=CVE-2024-58070 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58076 https://www.cve.org/CVERecord?id=CVE-2024-58076 Référence CVE CVE-2024-58077 https://www.cve.org/CVERecord?id=CVE-2024-58077 Référence CVE CVE-2024-58078 https://www.cve.org/CVERecord?id=CVE-2024-58078 Référence CVE CVE-2024-58079 https://www.cve.org/CVERecord?id=CVE-2024-58079 Référence CVE CVE-2024-58080 https://www.cve.org/CVERecord?id=CVE-2024-58080 Référence CVE CVE-2024-58081 https://www.cve.org/CVERecord?id=CVE-2024-58081 Référence CVE CVE-2024-58082 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0758Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-58055 Référence CVE CVE-2024-58056 https://www.cve.org/CVERecord?id=CVE-2024-58056 Référence CVE CVE-2024-58057 https://www.cve.org/CVERecord?id=CVE-2024-58057 Référence CVE CVE-2024-58058 https://www.cve.org/CVERecord?id=CVE-2024-58058 Référence CVE CVE-2024-58061 https://www.cve.org/CVERecord?id=CVE-2024-58061 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58068 https://www.cve.org/CVERecord?id=CVE-2024-58068 Référence CVE CVE-2024-58069 https://www.cve.org/CVERecord?id=CVE-2024-58069 Référence CVE CVE-2024-58070 https://www.cve.org/CVERecord?id=CVE-2024-58070 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58076 https://www.cve.org/CVERecord?id=CVE-2024-58076 Référence CVE CVE-2024-58077 https://www.cve.org/CVERecord?id=CVE-2024-58077 Référence CVE CVE-2024-58078 https://www.cve.org/CVERecord?id=CVE-2024-58078 Référence CVE CVE-2024-58079 https://www.cve.org/CVERecord?id=CVE-2024-58079 Référence CVE CVE-2024-58080 https://www.cve.org/CVERecord?id=CVE-2024-58080 Référence CVE CVE-2024-58081 https://www.cve.org/CVERecord?id=CVE-2024-58081 Référence CVE CVE-2024-58082 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0625Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-58055 Référence CVE CVE-2024-58056 https://www.cve.org/CVERecord?id=CVE-2024-58056 Référence CVE CVE-2024-58057 https://www.cve.org/CVERecord?id=CVE-2024-58057 Référence CVE CVE-2024-58058 https://www.cve.org/CVERecord?id=CVE-2024-58058 Référence CVE CVE-2024-58061 https://www.cve.org/CVERecord?id=CVE-2024-58061 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58068 https://www.cve.org/CVERecord?id=CVE-2024-58068 Référence CVE CVE-2024-58069 https://www.cve.org/CVERecord?id=CVE-2024-58069 Référence CVE CVE-2024-58070 https://www.cve.org/CVERecord?id=CVE-2024-58070 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58076 https://www.cve.org/CVERecord?id=CVE-2024-58076 Référence CVE CVE-2024-58077 https://www.cve.org/CVERecord?id=CVE-2024-58077 Référence CVE CVE-2024-58078 https://www.cve.org/CVERecord?id=CVE-2024-58078 Référence CVE CVE-2024-58079 https://www.cve.org/CVERecord?id=CVE-2024-58079 Référence CVE CVE-2024-58080 https://www.cve.org/CVERecord?id=CVE-2024-58080 Référence CVE CVE-2024-58081 https://www.cve.org/CVERecord?id=CVE-2024-58081 Référence CVE CVE-2024-58082 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0605Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-58014 Référence CVE CVE-2024-58017 https://www.cve.org/CVERecord?id=CVE-2024-58017 Référence CVE CVE-2024-58020 https://www.cve.org/CVERecord?id=CVE-2024-58020 Référence CVE CVE-2024-58051 https://www.cve.org/CVERecord?id=CVE-2024-58051 Référence CVE CVE-2024-58052 https://www.cve.org/CVERecord?id=CVE-2024-58052 Référence CVE CVE-2024-58055 https://www.cve.org/CVERecord?id=CVE-2024-58055 Référence CVE CVE-2024-58058 https://www.cve.org/CVERecord?id=CVE-2024-58058 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58069 https://www.cve.org/CVERecord?id=CVE-2024-58069 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2024-58085 https://www.cve.org/CVERecord?id=CVE-2024-58085 Référence CVE CVE-2024-58090 https://www.cve.org/CVERecord?id=CVE-2024-58090 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=CVE-2024-58093 Référence CVE CVE-2025-21647 https://www.cve.org/CVERecord?id=CVE-2025-21647 Référence CVE CVE-2025-21704 https://www.cve.org/CVERecord?id=CVE-2025-21704 Référence CVE CVE-2025-21708 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0559Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-58017 Référence CVE CVE-2024-58020 https://www.cve.org/CVERecord?id=CVE-2024-58020 Référence CVE CVE-2024-58034 https://www.cve.org/CVERecord?id=CVE-2024-58034 Référence CVE CVE-2024-58051 https://www.cve.org/CVERecord?id=CVE-2024-58051 Référence CVE CVE-2024-58052 https://www.cve.org/CVERecord?id=CVE-2024-58052 Référence CVE CVE-2024-58055 https://www.cve.org/CVERecord?id=CVE-2024-58055 Référence CVE CVE-2024-58058 https://www.cve.org/CVERecord?id=CVE-2024-58058 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58069 https://www.cve.org/CVERecord?id=CVE-2024-58069 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58076 https://www.cve.org/CVERecord?id=CVE-2024-58076 Référence CVE CVE-2024-58079 https://www.cve.org/CVERecord?id=CVE-2024-58079 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2024-58085 https://www.cve.org/CVERecord?id=CVE-2024-58085 Référence CVE CVE-2024-58086 https://www.cve.org/CVERecord?id=CVE-2024-58086 Référence CVE CVE-2024-58090 https://www.cve.org/CVERecord?id=CVE-2024-58090 Référence CVE CVE-2024-58092 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0529Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-57996 Référence CVE CVE-2024-57998 https://www.cve.org/CVERecord?id=CVE-2024-57998 Référence CVE CVE-2024-58001 https://www.cve.org/CVERecord?id=CVE-2024-58001 Référence CVE CVE-2024-58013 https://www.cve.org/CVERecord?id=CVE-2024-58013 Référence CVE CVE-2024-58018 https://www.cve.org/CVERecord?id=CVE-2024-58018 Référence CVE CVE-2024-58019 https://www.cve.org/CVERecord?id=CVE-2024-58019 Référence CVE CVE-2024-58020 https://www.cve.org/CVERecord?id=CVE-2024-58020 Référence CVE CVE-2024-58068 https://www.cve.org/CVERecord?id=CVE-2024-58068 Référence CVE CVE-2024-58070 https://www.cve.org/CVERecord?id=CVE-2024-58070 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58074 https://www.cve.org/CVERecord?id=CVE-2024-58074 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2024-58088 https://www.cve.org/CVERecord?id=CVE-2024-58088 Référence CVE CVE-2024-58091 https://www.cve.org/CVERecord?id=CVE-2024-58091 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=CVE-2024-58093 Référence CVE CVE-2024-58094 https://www.cve.org/CVERecord?id=CVE-2024-58094 Référence CVE CVE-2024-58095 https://www.cve.org/CVERecord?id=CVE-2024-58095 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0509Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-58055 Référence CVE CVE-2024-58056 https://www.cve.org/CVERecord?id=CVE-2024-58056 Référence CVE CVE-2024-58057 https://www.cve.org/CVERecord?id=CVE-2024-58057 Référence CVE CVE-2024-58058 https://www.cve.org/CVERecord?id=CVE-2024-58058 Référence CVE CVE-2024-58061 https://www.cve.org/CVERecord?id=CVE-2024-58061 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58068 https://www.cve.org/CVERecord?id=CVE-2024-58068 Référence CVE CVE-2024-58069 https://www.cve.org/CVERecord?id=CVE-2024-58069 Référence CVE CVE-2024-58070 https://www.cve.org/CVERecord?id=CVE-2024-58070 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58076 https://www.cve.org/CVERecord?id=CVE-2024-58076 Référence CVE CVE-2024-58078 https://www.cve.org/CVERecord?id=CVE-2024-58078 Référence CVE CVE-2024-58079 https://www.cve.org/CVERecord?id=CVE-2024-58079 Référence CVE CVE-2024-58080 https://www.cve.org/CVERecord?id=CVE-2024-58080 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2024-58085 https://www.cve.org/CVERecord?id=CVE-2024-58085 Référence CVE CVE-2024-58086 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0465Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-56650 Référence CVE CVE-2024-56702 https://www.cve.org/CVERecord?id=CVE-2024-56702 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57998 https://www.cve.org/CVERecord?id=CVE-2024-57998 Référence CVE CVE-2024-58001 https://www.cve.org/CVERecord?id=CVE-2024-58001 Référence CVE CVE-2024-58018 https://www.cve.org/CVERecord?id=CVE-2024-58018 Référence CVE CVE-2024-58068 https://www.cve.org/CVERecord?id=CVE-2024-58068 Référence CVE CVE-2024-58070 https://www.cve.org/CVERecord?id=CVE-2024-58070 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58088 https://www.cve.org/CVERecord?id=CVE-2024-58088 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=CVE-2024-58093 Référence CVE CVE-2024-58094 https://www.cve.org/CVERecord?id=CVE-2024-58094 Référence CVE CVE-2024-58095 https://www.cve.org/CVERecord?id=CVE-2024-58095 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2025-21683 https://www.cve.org/CVERecord?id=CVE-2025-21683 Référence CVE CVE-2025-21696 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0463Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2024-58016 Référence CVE CVE-2024-58017 https://www.cve.org/CVERecord?id=CVE-2024-58017 Référence CVE CVE-2024-58020 https://www.cve.org/CVERecord?id=CVE-2024-58020 Référence CVE CVE-2024-58051 https://www.cve.org/CVERecord?id=CVE-2024-58051 Référence CVE CVE-2024-58052 https://www.cve.org/CVERecord?id=CVE-2024-58052 Référence CVE CVE-2024-58055 https://www.cve.org/CVERecord?id=CVE-2024-58055 Référence CVE CVE-2024-58058 https://www.cve.org/CVERecord?id=CVE-2024-58058 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58069 https://www.cve.org/CVERecord?id=CVE-2024-58069 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58079 https://www.cve.org/CVERecord?id=CVE-2024-58079 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2024-58085 https://www.cve.org/CVERecord?id=CVE-2024-58085 Référence CVE CVE-2024-58090 https://www.cve.org/CVERecord?id=CVE-2024-58090 Référence CVE CVE-2025-21647 https://www.cve.org/CVERecord?id=CVE-2025-21647 Référence CVE CVE-2025-21700 https://www.cve.org/CVERecord?id=CVE-2025-21700 Référence CVE CVE-2025-21702 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0449Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-57998 Référence CVE CVE-2024-58001 https://www.cve.org/CVERecord?id=CVE-2024-58001 Référence CVE CVE-2024-58005 https://www.cve.org/CVERecord?id=CVE-2024-58005 Référence CVE CVE-2024-58009 https://www.cve.org/CVERecord?id=CVE-2024-58009 Référence CVE CVE-2024-58017 https://www.cve.org/CVERecord?id=CVE-2024-58017 Référence CVE CVE-2024-58018 https://www.cve.org/CVERecord?id=CVE-2024-58018 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58068 https://www.cve.org/CVERecord?id=CVE-2024-58068 Référence CVE CVE-2024-58070 https://www.cve.org/CVERecord?id=CVE-2024-58070 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58088 https://www.cve.org/CVERecord?id=CVE-2024-58088 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=CVE-2024-58093 Référence CVE CVE-2024-58094 https://www.cve.org/CVERecord?id=CVE-2024-58094 Référence CVE CVE-2024-58095 https://www.cve.org/CVERecord?id=CVE-2024-58095 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21683 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0336Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-56651 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57973 https://www.cve.org/CVERecord?id=CVE-2024-57973 Référence CVE CVE-2024-57979 https://www.cve.org/CVERecord?id=CVE-2024-57979 Référence CVE CVE-2024-57996 https://www.cve.org/CVERecord?id=CVE-2024-57996 Référence CVE CVE-2024-58013 https://www.cve.org/CVERecord?id=CVE-2024-58013 Référence CVE CVE-2024-58014 https://www.cve.org/CVERecord?id=CVE-2024-58014 Référence CVE CVE-2024-58052 https://www.cve.org/CVERecord?id=CVE-2024-58052 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2025-21693 https://www.cve.org/CVERecord?id=CVE-2025-21693 Référence CVE CVE-2025-21703 https://www.cve.org/CVERecord?id=CVE-2025-21703 Référence CVE CVE-2025-21708 https://www.cve.org/CVERecord?id=CVE-2025-21708 Référence CVE CVE-2025-21718 https://www.cve.org/CVERecord?id=CVE-2025-21718 Référence CVE CVE-2025-21744 https://www.cve.org/CVERecord?id=CVE-2025-21744 Référence CVE CVE-2025-21759 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0277Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2024-58052 Référence CVE CVE-2024-58054 https://www.cve.org/CVERecord?id=CVE-2024-58054 Référence CVE CVE-2024-58055 https://www.cve.org/CVERecord?id=CVE-2024-58055 Référence CVE CVE-2024-58056 https://www.cve.org/CVERecord?id=CVE-2024-58056 Référence CVE CVE-2024-58058 https://www.cve.org/CVERecord?id=CVE-2024-58058 Référence CVE CVE-2024-58061 https://www.cve.org/CVERecord?id=CVE-2024-58061 Référence CVE CVE-2024-58063 https://www.cve.org/CVERecord?id=CVE-2024-58063 Référence CVE CVE-2024-58068 https://www.cve.org/CVERecord?id=CVE-2024-58068 Référence CVE CVE-2024-58069 https://www.cve.org/CVERecord?id=CVE-2024-58069 Référence CVE CVE-2024-58071 https://www.cve.org/CVERecord?id=CVE-2024-58071 Référence CVE CVE-2024-58072 https://www.cve.org/CVERecord?id=CVE-2024-58072 Référence CVE CVE-2024-58076 https://www.cve.org/CVERecord?id=CVE-2024-58076 Référence CVE CVE-2024-58077 https://www.cve.org/CVERecord?id=CVE-2024-58077 Référence CVE CVE-2024-58080 https://www.cve.org/CVERecord?id=CVE-2024-58080 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2024-58085 https://www.cve.org/CVERecord?id=CVE-2024-58085 Référence CVE CVE-2024-58086 https://www.cve.org/CVERecord?id=CVE-2024-58086 Référence CVE CVE-2025-21684 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-021013Linux の Linux Kernel におけるリソースのロックに関する脆弱性

Linux の Linux Kernel には、リソースのロックに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 3.3, 5.4.291 ≤ 5.4.*, 5.10.235 ≤ 5.10.*, 5.15.179 ≤ 5.15.*, 6.1.129 ≤ 6.1.*, 6.6.76 ≤ 6.6.*, 6.12.13 ≤ 6.12.*, 6.13.2 ≤ 6.13.*, 6.14 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 6 Mar 2025 · Last source change 12 May 2026, 12:02 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-54029
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-54029↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-58071 · cve.blacktree.nl