CVE-2025-21888: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix a WARN during dereg_mr for DM type Memory regions (MR) of type DM (device memory) do not have an associated umem. In the __mlx5_ib_dereg_mr() -> mlx5_free_priv_descs() flow, the code incorrectly takes the wrong branch, attempting to call dma_unmap_single() on a DMA address that is not mapped. This results in a WARN [1], as shown below. The issue is resolved by properly accounting for the DM type and ensuring the correct branch is selected in mlx5_free_priv_descs(). [1] WARNING: CPU: 12 PID: 1346 at drivers/iommu/dma-iommu.c:1230 iommu_dma_unmap_page+0x79/0x90 Modules linked in: ip6table_mangle ip6table_nat ip6table_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 ovelay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core fuse mlx5_core CPU: 12 UID: 0 PID: 1346 Comm: ibv_rc_pingpong Not tainted 6.12.0-rc7+ #1631 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:iommu_dma_unmap_page+0x79/0x90 Code: 2b 49 3b 29 72 26 49 3b 69 08 73 20 4d 89 f0 44 89 e9 4c 89 e2 48 89 ee 48 89 df 5b 5d 41 5c 41 5d 41 5e 41 5f e9 07 b8 88 ff <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 66 0f 1f 44 00 RSP: 0018:ffffc90001913a10 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88810194b0a8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001 RBP: ffff88810194b0a8 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f537abdd740(0000) GS:ffff88885fb00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f537aeb8000 CR3: 000000010c248001 CR4: 0000000000372eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __warn+0x84/0x190 ? iommu_dma_unmap_page+0x79/0x90 ? report_bug+0xf8/0x1c0 ? handle_bug+0x55/0x90 ? exc_invalid_op+0x13/0x60 ? asm_exc_invalid_op+0x16/0x20 ? iommu_dma_unmap_page+0x79/0x90 dma_unmap_page_attrs+0xe6/0x290 mlx5_free_priv_descs+0xb0/0xe0 [mlx5_ib] __mlx5_ib_dereg_mr+0x37e/0x520 [mlx5_ib] ? _raw_spin_unlock_irq+0x24/0x40 ? wait_for_completion+0xfe/0x130 ? rdma_restrack_put+0x63/0xe0 [ib_core] ib_dereg_mr_user+0x5f/0x120 [ib_core] ? lock_release+0xc6/0x280 destroy_hw_idr_uobject+0x1d/0x60 [ib_uverbs] uverbs_destroy_uobject+0x58/0x1d0 [ib_uverbs] uobj_destroy+0x3f/0x70 [ib_uverbs] ib_uverbs_cmd_verbs+0x3e4/0xbb0 [ib_uverbs] ? __pfx_uverbs_destroy_def_handler+0x10/0x10 [ib_uverbs] ? lock_acquire+0xc1/0x2f0 ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0x116/0x170 [ib_uverbs] ? lock_release+0xc6/0x280 ib_uverbs_ioctl+0xe7/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] __x64_sys_ioctl+0x1b0/0xa70 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f537adaf17b Code: 0f 1e fa 48 8b 05 1d ad 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ed ac 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffff218f0b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffff218f1d8 RCX: 00007f537adaf17b RDX: 00007ffff218f1c0 RSI: 00000000c0181b01 RDI: 0000000000000003 RBP: 00007ffff218f1a0 R08: 00007f537aa8d010 R09: 0000561ee2e4f270 R10: 00007f537aace3a8 R11: 0000000000000246 R12: 00007ffff218f190 R13: 000000000000001c R14: 0000561ee2e4d7c0 R15: 00007ffff218f450 </TASK>
AI Analysis
Technical Summary
CVE-2025-21888 is a vulnerability identified in the Linux kernel, specifically within the RDMA (Remote Direct Memory Access) subsystem related to Mellanox mlx5 InfiniBand drivers. The flaw arises in the handling of memory regions (MR) of the device memory (DM) type during deregistration. In the deregistration flow (__mlx5_ib_dereg_mr() calling mlx5_free_priv_descs()), the code incorrectly assumes that all memory regions have an associated user memory (umem) and attempts to unmap a DMA address that was never mapped. This incorrect branch selection leads to a kernel warning (WARN) and potentially an invalid operation exception, as the function dma_unmap_single() is called on an unmapped DMA address. The root cause is a missing conditional check for the DM type MR, which lacks an associated umem, causing the erroneous code path to execute. The issue manifests as kernel warnings and could lead to system instability or crashes if triggered. The vulnerability was resolved by correcting the branch selection logic in mlx5_free_priv_descs() to properly account for DM type memory regions, preventing the invalid DMA unmapping call. The vulnerability affects Linux kernel versions including the 6.12.0-rc7+ release candidate and likely other versions containing the mlx5_ib driver with RDMA support. The vulnerability does not appear to have known exploits in the wild and requires kernel-level access to trigger, typically through RDMA user-space tools or drivers interacting with the mlx5 InfiniBand hardware. The detailed kernel stack trace shows the warning occurs in iommu_dma_unmap_page(), triggered during deregistration of memory regions by the ibv_rc_pingpong application or similar RDMA utilities.
Potential Impact
For European organizations, the impact of CVE-2025-21888 is primarily related to systems utilizing RDMA technology with Mellanox mlx5 InfiniBand adapters, common in high-performance computing (HPC), data centers, and enterprise environments requiring low-latency, high-throughput networking. The vulnerability can cause kernel warnings and potentially system instability or crashes, leading to denial of service (DoS) conditions on affected hosts. While it does not directly enable privilege escalation or remote code execution, the instability could disrupt critical services relying on RDMA, such as database clusters, virtualization platforms, or scientific computing workloads. Organizations in sectors like finance, research, telecommunications, and cloud service providers in Europe that deploy Linux servers with RDMA-enabled Mellanox hardware are at risk of operational disruptions. The vulnerability requires local or privileged user interaction to trigger, limiting remote exploitation but increasing risk in multi-tenant or shared environments where untrusted users may have access to RDMA interfaces. Given the increasing adoption of RDMA in European HPC and cloud infrastructures, the vulnerability could affect availability and reliability of critical systems if left unpatched.
Mitigation Recommendations
To mitigate CVE-2025-21888, European organizations should: 1) Apply the official Linux kernel patches that correct the mlx5_ib driver logic as soon as they become available, ensuring the fix is included in kernel versions deployed in production. 2) Audit and restrict access to RDMA user-space tools and interfaces, limiting usage to trusted administrators and applications to reduce the risk of triggering the vulnerability. 3) Monitor kernel logs for WARN messages related to iommu_dma_unmap_page or mlx5_ib deregistration failures to detect potential exploitation attempts or instability. 4) In environments where immediate patching is not feasible, consider disabling RDMA support or the mlx5_ib driver temporarily if RDMA functionality is not critical, to prevent exposure. 5) Coordinate with hardware vendors and Linux distribution maintainers to receive timely updates and guidance on this vulnerability. 6) Implement robust system monitoring and automated recovery mechanisms to minimize downtime in case of kernel crashes triggered by this issue.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Denmark, Switzerland, Italy, Spain
CVE-2025-21888: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix a WARN during dereg_mr for DM type Memory regions (MR) of type DM (device memory) do not have an associated umem. In the __mlx5_ib_dereg_mr() -> mlx5_free_priv_descs() flow, the code incorrectly takes the wrong branch, attempting to call dma_unmap_single() on a DMA address that is not mapped. This results in a WARN [1], as shown below. The issue is resolved by properly accounting for the DM type and ensuring the correct branch is selected in mlx5_free_priv_descs(). [1] WARNING: CPU: 12 PID: 1346 at drivers/iommu/dma-iommu.c:1230 iommu_dma_unmap_page+0x79/0x90 Modules linked in: ip6table_mangle ip6table_nat ip6table_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 ovelay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core fuse mlx5_core CPU: 12 UID: 0 PID: 1346 Comm: ibv_rc_pingpong Not tainted 6.12.0-rc7+ #1631 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:iommu_dma_unmap_page+0x79/0x90 Code: 2b 49 3b 29 72 26 49 3b 69 08 73 20 4d 89 f0 44 89 e9 4c 89 e2 48 89 ee 48 89 df 5b 5d 41 5c 41 5d 41 5e 41 5f e9 07 b8 88 ff <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 66 0f 1f 44 00 RSP: 0018:ffffc90001913a10 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88810194b0a8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001 RBP: ffff88810194b0a8 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f537abdd740(0000) GS:ffff88885fb00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f537aeb8000 CR3: 000000010c248001 CR4: 0000000000372eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __warn+0x84/0x190 ? iommu_dma_unmap_page+0x79/0x90 ? report_bug+0xf8/0x1c0 ? handle_bug+0x55/0x90 ? exc_invalid_op+0x13/0x60 ? asm_exc_invalid_op+0x16/0x20 ? iommu_dma_unmap_page+0x79/0x90 dma_unmap_page_attrs+0xe6/0x290 mlx5_free_priv_descs+0xb0/0xe0 [mlx5_ib] __mlx5_ib_dereg_mr+0x37e/0x520 [mlx5_ib] ? _raw_spin_unlock_irq+0x24/0x40 ? wait_for_completion+0xfe/0x130 ? rdma_restrack_put+0x63/0xe0 [ib_core] ib_dereg_mr_user+0x5f/0x120 [ib_core] ? lock_release+0xc6/0x280 destroy_hw_idr_uobject+0x1d/0x60 [ib_uverbs] uverbs_destroy_uobject+0x58/0x1d0 [ib_uverbs] uobj_destroy+0x3f/0x70 [ib_uverbs] ib_uverbs_cmd_verbs+0x3e4/0xbb0 [ib_uverbs] ? __pfx_uverbs_destroy_def_handler+0x10/0x10 [ib_uverbs] ? lock_acquire+0xc1/0x2f0 ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0x116/0x170 [ib_uverbs] ? lock_release+0xc6/0x280 ib_uverbs_ioctl+0xe7/0x170 [ib_uverbs] ? ib_uverbs_ioctl+0xcb/0x170 [ib_uverbs] __x64_sys_ioctl+0x1b0/0xa70 do_syscall_64+0x6b/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f537adaf17b Code: 0f 1e fa 48 8b 05 1d ad 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ed ac 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffff218f0b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffff218f1d8 RCX: 00007f537adaf17b RDX: 00007ffff218f1c0 RSI: 00000000c0181b01 RDI: 0000000000000003 RBP: 00007ffff218f1a0 R08: 00007f537aa8d010 R09: 0000561ee2e4f270 R10: 00007f537aace3a8 R11: 0000000000000246 R12: 00007ffff218f190 R13: 000000000000001c R14: 0000561ee2e4d7c0 R15: 00007ffff218f450 </TASK>
AI-Powered Analysis
Technical Analysis
CVE-2025-21888 is a vulnerability identified in the Linux kernel, specifically within the RDMA (Remote Direct Memory Access) subsystem related to Mellanox mlx5 InfiniBand drivers. The flaw arises in the handling of memory regions (MR) of the device memory (DM) type during deregistration. In the deregistration flow (__mlx5_ib_dereg_mr() calling mlx5_free_priv_descs()), the code incorrectly assumes that all memory regions have an associated user memory (umem) and attempts to unmap a DMA address that was never mapped. This incorrect branch selection leads to a kernel warning (WARN) and potentially an invalid operation exception, as the function dma_unmap_single() is called on an unmapped DMA address. The root cause is a missing conditional check for the DM type MR, which lacks an associated umem, causing the erroneous code path to execute. The issue manifests as kernel warnings and could lead to system instability or crashes if triggered. The vulnerability was resolved by correcting the branch selection logic in mlx5_free_priv_descs() to properly account for DM type memory regions, preventing the invalid DMA unmapping call. The vulnerability affects Linux kernel versions including the 6.12.0-rc7+ release candidate and likely other versions containing the mlx5_ib driver with RDMA support. The vulnerability does not appear to have known exploits in the wild and requires kernel-level access to trigger, typically through RDMA user-space tools or drivers interacting with the mlx5 InfiniBand hardware. The detailed kernel stack trace shows the warning occurs in iommu_dma_unmap_page(), triggered during deregistration of memory regions by the ibv_rc_pingpong application or similar RDMA utilities.
Potential Impact
For European organizations, the impact of CVE-2025-21888 is primarily related to systems utilizing RDMA technology with Mellanox mlx5 InfiniBand adapters, common in high-performance computing (HPC), data centers, and enterprise environments requiring low-latency, high-throughput networking. The vulnerability can cause kernel warnings and potentially system instability or crashes, leading to denial of service (DoS) conditions on affected hosts. While it does not directly enable privilege escalation or remote code execution, the instability could disrupt critical services relying on RDMA, such as database clusters, virtualization platforms, or scientific computing workloads. Organizations in sectors like finance, research, telecommunications, and cloud service providers in Europe that deploy Linux servers with RDMA-enabled Mellanox hardware are at risk of operational disruptions. The vulnerability requires local or privileged user interaction to trigger, limiting remote exploitation but increasing risk in multi-tenant or shared environments where untrusted users may have access to RDMA interfaces. Given the increasing adoption of RDMA in European HPC and cloud infrastructures, the vulnerability could affect availability and reliability of critical systems if left unpatched.
Mitigation Recommendations
To mitigate CVE-2025-21888, European organizations should: 1) Apply the official Linux kernel patches that correct the mlx5_ib driver logic as soon as they become available, ensuring the fix is included in kernel versions deployed in production. 2) Audit and restrict access to RDMA user-space tools and interfaces, limiting usage to trusted administrators and applications to reduce the risk of triggering the vulnerability. 3) Monitor kernel logs for WARN messages related to iommu_dma_unmap_page or mlx5_ib deregistration failures to detect potential exploitation attempts or instability. 4) In environments where immediate patching is not feasible, consider disabling RDMA support or the mlx5_ib driver temporarily if RDMA functionality is not critical, to prevent exposure. 5) Coordinate with hardware vendors and Linux distribution maintainers to receive timely updates and guidance on this vulnerability. 6) Implement robust system monitoring and automated recovery mechanisms to minimize downtime in case of kernel crashes triggered by this issue.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-12-29T08:45:45.782Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9832c4522896dcbe8b0c
Added to database: 5/21/2025, 9:09:06 AM
Last enriched: 6/30/2025, 10:25:02 AM
Last updated: 8/8/2025, 2:17:40 PM
Views: 15
Related Threats
CVE-2025-8991: Business Logic Errors in linlinjava litemall
MediumCVE-2025-8990: SQL Injection in code-projects Online Medicine Guide
MediumCVE-2025-8940: Buffer Overflow in Tenda AC20
HighCVE-2025-8939: Buffer Overflow in Tenda AC20
HighCVE-2025-50518: n/a
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.