{"id":"CVE-2025-21714","title":"RDMA/mlx5: Fix implicit ODP use after free","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix implicit ODP use after free\n\nPrevent double queueing of implicit ODP mr destroy work by using\n__xa_cmpxchg() to make sure this is the only time we are de…","severity":"high","cvss":7.8,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= 5256edcb98a14b11409a2d323f56a70a8b366363 < a306dfff6b76aafa264ad33874a8992a8d5858b7","Linux >= 5256edcb98a14b11409a2d323f56a70a8b366363 < 7cc8f681f6d4ae4478ae0f60485fc768f2b450da","Linux >= 5256edcb98a14b11409a2d323f56a70a8b366363 < edfb65dbb9ffd3102f3ff4dd21316158e56f1976","Linux >= 5256edcb98a14b11409a2d323f56a70a8b366363 < d3d930411ce390e532470194296658a960887773","Linux 5.5"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total","timestamp":"2025-02-27T18:14:41.666348Z"},"published":"2025-02-27","updated":"2026-10-21","sourceUpdated":"2026-10-21T12:35:55.119Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-21714","references":[{"url":"https://git.kernel.org/stable/c/a306dfff6b76aafa264ad33874a8992a8d5858b7"},{"url":"https://git.kernel.org/stable/c/7cc8f681f6d4ae4478ae0f60485fc768f2b450da"},{"url":"https://git.kernel.org/stable/c/edfb65dbb9ffd3102f3ff4dd21316158e56f1976"},{"url":"https://git.kernel.org/stable/c/d3d930411ce390e532470194296658a960887773"}],"tags":["cve.org"],"epss":0.00241,"epssPercentile":0.15108,"ingestedAt":"2026-10-21T12:48:53.719Z","slug":"CVE-2025-21714","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix implicit ODP use after free\n\nPrevent double queueing of implicit ODP mr destroy work by using\n__xa_cmpxchg() to make sure this is the only time we are destroying this\nspecific mr.\n\nWithout this change, we could try to invalidate this mr twice, which in\nturn could result in queuing a MR work destroy twice, and eventually the\nsecond work could execute after the MR was freed due to the first work,\ncausing a user after free and trace below.\n\n   refcount_t: underflow; use-after-free.\n   WARNING: CPU: 2 PID: 12178 at lib/refcount.c:28 refcount_warn_saturate+0x12b/0x130\n   Modules linked in: bonding ib_ipoib vfio_pci ip_gre geneve nf_tables ip6_gre gre ip6_tunnel tunnel6 ipip tunnel4 ib_umad rdma_ucm mlx5_vfio_pci vfio_pci_core vfio_iommu_type1 mlx5_ib vfio ib_uverbs mlx5_core iptable_raw openvswitch nsh rpcrdma ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_cm ib_core xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay zram zsmalloc fuse [last unloaded: ib_uverbs]\n   CPU: 2 PID: 12178 Comm: kworker/u20:5 Not tainted 6.5.0-rc1_net_next_mlx5_58c644e #1\n   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n   Workqueue: events_unbound free_implicit_child_mr_work [mlx5_ib]\n   RIP: 0010:refcount_warn_saturate+0x12b/0x130\n   Code: 48 c7 c7 38 95 2a 82 c6 05 bc c6 fe 00 01 e8 0c 66 aa ff 0f 0b 5b c3 48 c7 c7 e0 94 2a 82 c6 05 a7 c6 fe 00 01 e8 f5 65 aa ff <0f> 0b 5b c3 90 8b 07 3d 00 00 00 c0 74 12 83 f8 01 74 13 8d 50 ff\n   RSP: 0018:ffff8881008e3e40 EFLAGS: 00010286\n   RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027\n   RDX: ffff88852c91b5c8 RSI: 0000000000000001 RDI: ffff88852c91b5c0\n   RBP: ffff8881dacd4e00 R08: 00000000ffffffff R09: 0000000000000019\n   R10: 000000000000072e R11: 0000000063666572 R12: ffff88812bfd9e00\n   R13: ffff8881c792d200 R14: ffff88810011c005 R15: ffff8881002099c0\n   FS:  0000000000000000(0000) GS:ffff88852c900000(0000) knlGS:0000000000000000\n   CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n   CR2: 00007f5694b5e000 CR3: 00000001153f6003 CR4: 0000000000370ea0\n   DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n   DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n   Call Trace:\n    <TASK>\n    ? refcount_warn_saturate+0x12b/0x130\n    free_implicit_child_mr_work+0x180/0x1b0 [mlx5_ib]\n    process_one_work+0x1cc/0x3c0\n    worker_thread+0x218/0x3c0\n    kthread+0xc6/0xf0\n    ret_from_fork+0x1f/0x30\n    </TASK>\n\n## Affected\n\n- `Linux >= 5256edcb98a14b11409a2d323f56a70a8b366363 < a306dfff6b76aafa264ad33874a8992a8d5858b7`\n- `Linux >= 5256edcb98a14b11409a2d323f56a70a8b366363 < 7cc8f681f6d4ae4478ae0f60485fc768f2b450da`\n- `Linux >= 5256edcb98a14b11409a2d323f56a70a8b366363 < edfb65dbb9ffd3102f3ff4dd21316158e56f1976`\n- `Linux >= 5256edcb98a14b11409a2d323f56a70a8b366363 < d3d930411ce390e532470194296658a960887773`\n- `Linux 5.5`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":43,"depthScoreParts":{"impact":42.9,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}