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

RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error

Linux · Linux

4.7MediumCVSS 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 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.14% 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 20 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.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.15-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
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-2025-5202

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: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error This patch addresses a race condition for an ODP MR that can result in a CQE with an error on the UMR QP. During the __mlx5_ib_dereg_mr() flow, the following sequence of calls occurs: mlx5_revoke_mr() mlx5r_umr_revoke_mr() mlx5r_umr_post_send_wait() At this point, the lkey is freed from the hardware's perspective. However, concurrently, mlx5_ib_invalidate_range() might be triggered by another task attempting to invalidate a range for the same freed lkey. This task will: - Acquire the umem_odp->umem_mutex lock. - Call mlx5r_umr_update_xlt() on the UMR QP. - Since the lkey has already been freed, this can lead to a CQE error, causing the UMR QP to enter an error state [1]. To resolve this race condition, the umem_odp->umem_mutex lock is now also acquired as part of the mlx5_revoke_mr() scope. Upon successful revoke, we set umem_odp->private which points to that MR to NULL, preventing any further invalidation attempts on its lkey. [1] From dmesg: infiniband rocep8s0f0: dump_cqe:277:(pid 0): WC error: 6, Message: memory bind operation error cqe_dump: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000030: 00 00 00 00 08 00 78 06 25 00 11 b9 00 0e dd d2 WARNING: CPU: 15 PID: 1506 at drivers/infiniband/hw/mlx5/umr.c:394 mlx5r_umr_post_send_wait+0x15a/0x2b0 [mlx5_ib] Modules linked in: ip6table_mangle ip6table_natip6table_filter ip6_tables iptable_mangle xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_umad ib_ipoib ib_cm mlx5_ib ib_uverbs ib_core fuse mlx5_core CPU: 15 UID: 0 PID: 1506 Comm: ibv_rc_pingpong Not tainted 6.12.0-rc7+ #1626 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:mlx5r_umr_post_send_wait+0x15a/0x2b0 [mlx5_ib] [..] Call Trace: <TASK> mlx5r_umr_update_xlt+0x23c/0x3e0 [mlx5_ib] mlx5_ib_invalidate_range+0x2e1/0x330 [mlx5_ib] __mmu_notifier_invalidate_range_start+0x1e1/0x240 zap_page_range_single+0xf1/0x1a0 madvise_vma_behavior+0x677/0x6e0 do_madvise+0x1a2/0x4b0 __x64_sys_madvise+0x25/0x30 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e

What

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error This patch addresses a race condition for an ODP MR that can result in a CQE with an error on the UMR QP. During the __mlx5_ib_dereg_mr() flow, the following sequence of calls occurs: mlx5_revoke_mr() mlx5r_umr_revoke_mr() mlx5r_umr_post_send_wait() At this point, the lkey is freed from the hardware's perspective. However, concurrently, mlx5_ib_invalidate_range() might be triggered by another task attempting to invalidate a range for the same freed lkey. This task will: - Acquire the umem_odp->umem_mutex lock. - Call mlx5r_umr_update_xlt() on the UMR QP. - Since the lkey has already been freed, this can lead to a CQE error, causing the UMR QP to enter an error state [1]. To resolve this race condition, the umem_odp->umem_mutex lock is now also acquired as part of the mlx5_revoke_mr() scope. Upon successful revoke, we set umem_odp->private which points to that MR to NULL, preventing any further invalidation attempts on its lkey. [1] From dmesg: infiniband rocep8s0f0: dump_cqe:277:(pid 0): WC error: 6, Message: memory bind operation error cqe_dump: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000030: 00 00 00 00 08 00 78 06 25 00 11 b9 00 0e dd d2 WARNING: CPU: 15 PID: 1506 at drivers/infiniband/hw/mlx5/umr.c:394 mlx5r_umr_post_send_wait+0x15a/0x2b0 [mlx5_ib] Modules linked in: ip6table_mangle ip6table_natip6table_filter ip6_tables iptable_mangle xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_umad ib_ipoib ib_cm mlx5_ib ib_uverbs ib_core fuse mlx5_core CPU: 15 UID: 0 PID: 1506 Comm: ibv_rc_pingpong Not tainted 6.12.0-rc7+ #1626 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:mlx5r_umr_post_send_wait+0x15a/0x2b0 [mlx5_ib] [..] Call Trace: <TASK> mlx5r_umr_update_xlt+0x23c/0x3e0 [mlx5_ib] mlx5_ib_invalidate_range+0x2e1/0x330 [mlx5_ib] __mmu_notifier_invalidate_range_start+0x1e1/0x240 zap_page_range_single+0xf1/0x1a0 madvise_vma_behavior+0x677/0x6e0 do_madvise+0x1a2/0x4b0 __x64_sys_madvise+0x25/0x30 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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: RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error This patch addresses a race condition for an ODP MR that can result in a CQE with an error on the UMR QP. During the __mlx5_ib_dereg_mr() flow, the following sequence of calls occurs: mlx5_revoke_mr() mlx5r_umr_revoke_mr() mlx5r_umr_post_send_wait() At this point, the lkey is freed from the hardware's perspective. However, concurrently, mlx5_ib_invalidate_range() might be triggered by another task attempting to invalidate a range for the same freed lkey. This task will: - Acquire the umem_odp->umem_mutex lock. - Call mlx5r_umr_update_xlt() on the UMR QP. - Since the lkey has already been freed, this can lead to a CQE error, causing the UMR QP to enter an error state [1]. To resolve this race condition, the umem_odp->umem_mutex lock is now also acquired as part of the mlx5_revoke_mr() scope. Upon successful revoke, we set umem_odp->private which points to that MR to NULL, preventing any further invalidation attempts on its lkey. [1] From dmesg: infiniband rocep8s0f0: dump_cqe:277:(pid 0): WC error: 6, Message: memory bind operation error cqe_dump: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cqe_dump: 00000030: 00 00 00 00 08 00 78 06 25 00 11 b9 00 0e dd d2 WARNING: CPU: 15 PID: 1506 at drivers/infiniband/hw/mlx5/umr.c:394 mlx5r_umr_post_send_wait+0x15a/0x2b0 [mlx5_ib] Modules linked in: ip6table_mangle ip6table_natip6table_filter ip6_tables iptable_mangle xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_umad ib_ipoib ib_cm mlx5_ib ib_uverbs ib_core fuse mlx5_core CPU: 15 UID: 0 PID: 1506 Comm: ibv_rc_pingpong Not tainted 6.12.0-rc7+ #1626 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:mlx5r_umr_post_send_wait+0x15a/0x2b0 [mlx5_ib] [..] Call Trace: <TASK> mlx5r_umr_update_xlt+0x23c/0x3e0 [mlx5_ib] mlx5_ib_invalidate_range+0x2e1/0x330 [mlx5_ib] __mmu_notifier_invalidate_range_start+0x1e1/0x240 zap_page_range_single+0xf1/0x1a0 madvise_vma_behavior+0x677/0x6e0 do_madvise+0x1a2/0x4b0 __x64_sys_madvise+0x25/0x30 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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
High: exploitation depends on specific conditions
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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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-362
A

Official authority intelligence

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

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

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250305Security Bulletin 5 March 2025

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

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

d?id=CVE-2025-21672 Référence CVE CVE-2025-21673 https://www.cve.org/CVERecord?id=CVE-2025-21673 Référence CVE CVE-2025-21682 https://www.cve.org/CVERecord?id=CVE-2025-21682 Référence CVE CVE-2025-21693 https://www.cve.org/CVERecord?id=CVE-2025-21693 Référence CVE CVE-2025-21696 https://www.cve.org/CVERecord?id=CVE-2025-21696 Référence CVE CVE-2025-21712 https://www.cve.org/CVERecord?id=CVE-2025-21712 Référence CVE CVE-2025-21714 https://www.cve.org/CVERecord?id=CVE-2025-21714 Référence CVE CVE-2025-21723 https://www.cve.org/CVERecord?id=CVE-2025-21723 Référence CVE CVE-2025-21730 https://www.cve.org/CVERecord?id=CVE-2025-21730 Référence CVE CVE-2025-21732 https://www.cve.org/CVERecord?id=CVE-2025-21732 Référence CVE CVE-2025-21734 https://www.cve.org/CVERecord?id=CVE-2025-21734 Référence CVE CVE-2025-21738 https://www.cve.org/CVERecord?id=CVE-2025-21738 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21750 https://www.cve.org/CVERecord?id=CVE-2025-21750 Référence CVE CVE-2025-21751 https://www.cve.org/CVERecord?id=CVE-2025-21751 Référence CVE CVE-2025-21752 https://www.cve.org/CVERecord?id=CVE-2025-21752 Référence CVE CVE-2025-21759 https://www.cve.org/CVERecord?id=CVE-2025-21759 Référence CVE CVE-2025-21768 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21672 Référence CVE CVE-2025-21673 https://www.cve.org/CVERecord?id=CVE-2025-21673 Référence CVE CVE-2025-21682 https://www.cve.org/CVERecord?id=CVE-2025-21682 Référence CVE CVE-2025-21693 https://www.cve.org/CVERecord?id=CVE-2025-21693 Référence CVE CVE-2025-21696 https://www.cve.org/CVERecord?id=CVE-2025-21696 Référence CVE CVE-2025-21712 https://www.cve.org/CVERecord?id=CVE-2025-21712 Référence CVE CVE-2025-21714 https://www.cve.org/CVERecord?id=CVE-2025-21714 Référence CVE CVE-2025-21723 https://www.cve.org/CVERecord?id=CVE-2025-21723 Référence CVE CVE-2025-21730 https://www.cve.org/CVERecord?id=CVE-2025-21730 Référence CVE CVE-2025-21732 https://www.cve.org/CVERecord?id=CVE-2025-21732 Référence CVE CVE-2025-21734 https://www.cve.org/CVERecord?id=CVE-2025-21734 Référence CVE CVE-2025-21738 https://www.cve.org/CVERecord?id=CVE-2025-21738 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21750 https://www.cve.org/CVERecord?id=CVE-2025-21750 Référence CVE CVE-2025-21751 https://www.cve.org/CVERecord?id=CVE-2025-21751 Référence CVE CVE-2025-21752 https://www.cve.org/CVERecord?id=CVE-2025-21752 Référence CVE CVE-2025-21759 https://www.cve.org/CVERecord?id=CVE-2025-21759 Référence CVE CVE-2025-21768 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21705 Référence CVE CVE-2025-21706 https://www.cve.org/CVERecord?id=CVE-2025-21706 Référence CVE CVE-2025-21707 https://www.cve.org/CVERecord?id=CVE-2025-21707 Référence CVE CVE-2025-21709 https://www.cve.org/CVERecord?id=CVE-2025-21709 Référence CVE CVE-2025-21713 https://www.cve.org/CVERecord?id=CVE-2025-21713 Référence CVE CVE-2025-21716 https://www.cve.org/CVERecord?id=CVE-2025-21716 Référence CVE CVE-2025-21723 https://www.cve.org/CVERecord?id=CVE-2025-21723 Référence CVE CVE-2025-21724 https://www.cve.org/CVERecord?id=CVE-2025-21724 Référence CVE CVE-2025-21725 https://www.cve.org/CVERecord?id=CVE-2025-21725 Référence CVE CVE-2025-21732 https://www.cve.org/CVERecord?id=CVE-2025-21732 Référence CVE CVE-2025-21770 https://www.cve.org/CVERecord?id=CVE-2025-21770 Référence CVE CVE-2025-21783 https://www.cve.org/CVERecord?id=CVE-2025-21783 Référence CVE CVE-2025-21790 https://www.cve.org/CVERecord?id=CVE-2025-21790 Référence CVE CVE-2025-21795 https://www.cve.org/CVERecord?id=CVE-2025-21795 Référence CVE CVE-2025-21807 https://www.cve.org/CVERecord?id=CVE-2025-21807 Référence CVE CVE-2025-21808 https://www.cve.org/CVERecord?id=CVE-2025-21808 Référence CVE CVE-2025-21809 https://www.cve.org/CVERecord?id=CVE-2025-21809 Référence CVE CVE-2025-21810 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21721 Référence CVE CVE-2025-21722 https://www.cve.org/CVERecord?id=CVE-2025-21722 Référence CVE CVE-2025-21723 https://www.cve.org/CVERecord?id=CVE-2025-21723 Référence CVE CVE-2025-21724 https://www.cve.org/CVERecord?id=CVE-2025-21724 Référence CVE CVE-2025-21725 https://www.cve.org/CVERecord?id=CVE-2025-21725 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21727 https://www.cve.org/CVERecord?id=CVE-2025-21727 Référence CVE CVE-2025-21728 https://www.cve.org/CVERecord?id=CVE-2025-21728 Référence CVE CVE-2025-21731 https://www.cve.org/CVERecord?id=CVE-2025-21731 Référence CVE CVE-2025-21732 https://www.cve.org/CVERecord?id=CVE-2025-21732 Référence CVE CVE-2025-21733 https://www.cve.org/CVERecord?id=CVE-2025-21733 Référence CVE CVE-2025-21734 https://www.cve.org/CVERecord?id=CVE-2025-21734 Référence CVE CVE-2025-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21736 https://www.cve.org/CVERecord?id=CVE-2025-21736 Référence CVE CVE-2025-21738 https://www.cve.org/CVERecord?id=CVE-2025-21738 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21741 https://www.cve.org/CVERecord?id=CVE-2025-21741 Référence CVE CVE-2025-21742 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-2025-21721 Référence CVE CVE-2025-21722 https://www.cve.org/CVERecord?id=CVE-2025-21722 Référence CVE CVE-2025-21723 https://www.cve.org/CVERecord?id=CVE-2025-21723 Référence CVE CVE-2025-21724 https://www.cve.org/CVERecord?id=CVE-2025-21724 Référence CVE CVE-2025-21725 https://www.cve.org/CVERecord?id=CVE-2025-21725 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21727 https://www.cve.org/CVERecord?id=CVE-2025-21727 Référence CVE CVE-2025-21728 https://www.cve.org/CVERecord?id=CVE-2025-21728 Référence CVE CVE-2025-21731 https://www.cve.org/CVERecord?id=CVE-2025-21731 Référence CVE CVE-2025-21732 https://www.cve.org/CVERecord?id=CVE-2025-21732 Référence CVE CVE-2025-21733 https://www.cve.org/CVERecord?id=CVE-2025-21733 Référence CVE CVE-2025-21734 https://www.cve.org/CVERecord?id=CVE-2025-21734 Référence CVE CVE-2025-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21736 https://www.cve.org/CVERecord?id=CVE-2025-21736 Référence CVE CVE-2025-21738 https://www.cve.org/CVERecord?id=CVE-2025-21738 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21741 https://www.cve.org/CVERecord?id=CVE-2025-21741 Référence CVE CVE-2025-21742 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-2025-21721 Référence CVE CVE-2025-21722 https://www.cve.org/CVERecord?id=CVE-2025-21722 Référence CVE CVE-2025-21723 https://www.cve.org/CVERecord?id=CVE-2025-21723 Référence CVE CVE-2025-21724 https://www.cve.org/CVERecord?id=CVE-2025-21724 Référence CVE CVE-2025-21725 https://www.cve.org/CVERecord?id=CVE-2025-21725 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21727 https://www.cve.org/CVERecord?id=CVE-2025-21727 Référence CVE CVE-2025-21728 https://www.cve.org/CVERecord?id=CVE-2025-21728 Référence CVE CVE-2025-21731 https://www.cve.org/CVERecord?id=CVE-2025-21731 Référence CVE CVE-2025-21732 https://www.cve.org/CVERecord?id=CVE-2025-21732 Référence CVE CVE-2025-21733 https://www.cve.org/CVERecord?id=CVE-2025-21733 Référence CVE CVE-2025-21734 https://www.cve.org/CVERecord?id=CVE-2025-21734 Référence CVE CVE-2025-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21736 https://www.cve.org/CVERecord?id=CVE-2025-21736 Référence CVE CVE-2025-21738 https://www.cve.org/CVERecord?id=CVE-2025-21738 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21741 https://www.cve.org/CVERecord?id=CVE-2025-21741 Référence CVE CVE-2025-21742 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-2025-21719 Référence CVE CVE-2025-21723 https://www.cve.org/CVERecord?id=CVE-2025-21723 Référence CVE CVE-2025-21724 https://www.cve.org/CVERecord?id=CVE-2025-21724 Référence CVE CVE-2025-21725 https://www.cve.org/CVERecord?id=CVE-2025-21725 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21727 https://www.cve.org/CVERecord?id=CVE-2025-21727 Référence CVE CVE-2025-21728 https://www.cve.org/CVERecord?id=CVE-2025-21728 Référence CVE CVE-2025-21729 https://www.cve.org/CVERecord?id=CVE-2025-21729 Référence CVE CVE-2025-21731 https://www.cve.org/CVERecord?id=CVE-2025-21731 Référence CVE CVE-2025-21732 https://www.cve.org/CVERecord?id=CVE-2025-21732 Référence CVE CVE-2025-21733 https://www.cve.org/CVERecord?id=CVE-2025-21733 Référence CVE CVE-2025-21734 https://www.cve.org/CVERecord?id=CVE-2025-21734 Référence CVE CVE-2025-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21736 https://www.cve.org/CVERecord?id=CVE-2025-21736 Référence CVE CVE-2025-21738 https://www.cve.org/CVERecord?id=CVE-2025-21738 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21741 https://www.cve.org/CVERecord?id=CVE-2025-21741 Référence CVE CVE-2025-21742 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21706 Référence CVE CVE-2025-21708 https://www.cve.org/CVERecord?id=CVE-2025-21708 Référence CVE CVE-2025-21711 https://www.cve.org/CVERecord?id=CVE-2025-21711 Référence CVE CVE-2025-21714 https://www.cve.org/CVERecord?id=CVE-2025-21714 Référence CVE CVE-2025-21718 https://www.cve.org/CVERecord?id=CVE-2025-21718 Référence CVE CVE-2025-21723 https://www.cve.org/CVERecord?id=CVE-2025-21723 Référence CVE CVE-2025-21726 https://www.cve.org/CVERecord?id=CVE-2025-21726 Référence CVE CVE-2025-21727 https://www.cve.org/CVERecord?id=CVE-2025-21727 Référence CVE CVE-2025-21731 https://www.cve.org/CVERecord?id=CVE-2025-21731 Référence CVE CVE-2025-21732 https://www.cve.org/CVERecord?id=CVE-2025-21732 Référence CVE CVE-2025-21733 https://www.cve.org/CVERecord?id=CVE-2025-21733 Référence CVE CVE-2025-21734 https://www.cve.org/CVERecord?id=CVE-2025-21734 Référence CVE CVE-2025-21735 https://www.cve.org/CVERecord?id=CVE-2025-21735 Référence CVE CVE-2025-21736 https://www.cve.org/CVERecord?id=CVE-2025-21736 Référence CVE CVE-2025-21738 https://www.cve.org/CVERecord?id=CVE-2025-21738 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21741 https://www.cve.org/CVERecord?id=CVE-2025-21741 Référence CVE CVE-2025-21742 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-017813Linux の 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
Linux: e6fb246ccafbdfc86e0750af021628132fdbceac < b13d32786acabf70a7b04ed24b7468fc3c82977c, e6fb246ccafbdfc86e0750af021628132fdbceac < 5297f5ddffef47b94172ab0d3d62270002a3dcc1, e6fb246ccafbdfc86e0750af021628132fdbceac < abb604a1a9c87255c7a6f3b784410a9707baf467, 5.13
Fixed
Linux: < 5.13, 6.12.14 ≤ 6.12.*, 6.13.3 ≤ 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 27 Feb 2025 · Last source change 11 May 2026, 21:05 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-2025-5202
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

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-2025-5202↗CVE authority or vendor 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-2025-21732 · cve.blacktree.nl