Skip to main content

CVE-2025-21885: Vulnerability in Linux Linux

High
VulnerabilityCVE-2025-21885cvecve-2025-21885
Published: Thu Mar 27 2025 (03/27/2025, 14:57:13 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix the page details for the srq created by kernel consumers While using nvme target with use_srq on, below kernel panic is noticed. [ 549.698111] bnxt_en 0000:41:00.0 enp65s0np0: FEC autoneg off encoding: Clause 91 RS(544,514) [ 566.393619] Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI .. [ 566.393799] <TASK> [ 566.393807] ? __die_body+0x1a/0x60 [ 566.393823] ? die+0x38/0x60 [ 566.393835] ? do_trap+0xe4/0x110 [ 566.393847] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393867] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393881] ? do_error_trap+0x7c/0x120 [ 566.393890] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393911] ? exc_divide_error+0x34/0x50 [ 566.393923] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393939] ? asm_exc_divide_error+0x16/0x20 [ 566.393966] ? bnxt_qplib_alloc_init_hwq+0x1d4/0x580 [bnxt_re] [ 566.393997] bnxt_qplib_create_srq+0xc9/0x340 [bnxt_re] [ 566.394040] bnxt_re_create_srq+0x335/0x3b0 [bnxt_re] [ 566.394057] ? srso_return_thunk+0x5/0x5f [ 566.394068] ? __init_swait_queue_head+0x4a/0x60 [ 566.394090] ib_create_srq_user+0xa7/0x150 [ib_core] [ 566.394147] nvmet_rdma_queue_connect+0x7d0/0xbe0 [nvmet_rdma] [ 566.394174] ? lock_release+0x22c/0x3f0 [ 566.394187] ? srso_return_thunk+0x5/0x5f Page size and shift info is set only for the user space SRQs. Set page size and page shift for kernel space SRQs also.

AI-Powered Analysis

AILast updated: 06/30/2025, 10:24:34 UTC

Technical Analysis

CVE-2025-21885 is a vulnerability identified in the Linux kernel, specifically affecting the RDMA (Remote Direct Memory Access) subsystem's bnxt_re driver, which is used for Broadcom NetXtreme network adapters. The issue arises when using the NVMe target with the use_srq (Shared Receive Queue) option enabled. The vulnerability is due to improper handling of page size and page shift information for kernel space SRQs, which was previously only set for user space SRQs. This misconfiguration leads to kernel panics caused by divide errors during the creation of SRQs by kernel consumers. The kernel panic logs indicate a failure in the bnxt_qplib_create_srq function, which is responsible for allocating and initializing hardware queues. The root cause is that page size and shift details are not correctly set for kernel space SRQs, leading to erroneous calculations and ultimately a system crash. This vulnerability can cause denial of service (DoS) conditions by crashing the kernel, impacting system availability. Since the flaw is in the kernel driver handling RDMA and NVMe target configurations, it affects systems using these features, particularly those leveraging high-performance storage and networking setups. The vulnerability does not require user interaction but does require the use of specific kernel features (NVMe target with use_srq enabled). No known exploits are reported in the wild as of the publication date. The fix involves setting the page size and page shift correctly for kernel space SRQs, aligning with the handling for user space SRQs.

Potential Impact

For European organizations, the impact of CVE-2025-21885 can be significant, especially for enterprises and data centers relying on Linux servers with RDMA-enabled Broadcom network adapters and NVMe storage targets. The vulnerability can cause unexpected kernel panics leading to system crashes and downtime, which affects availability of critical services. Industries such as finance, telecommunications, cloud service providers, and research institutions that use high-performance computing and storage infrastructure are particularly at risk. The denial of service caused by kernel panics can disrupt business operations, lead to data unavailability, and increase operational costs due to system recovery and troubleshooting. Although no direct data breach or privilege escalation is indicated, the loss of availability can indirectly impact confidentiality and integrity if systems are taken offline during attacks or failures. The lack of known exploits reduces immediate risk, but the complexity of the environment and the critical nature of affected systems mean that timely patching is essential to prevent potential exploitation or accidental crashes.

Mitigation Recommendations

1. Apply the official Linux kernel patches that address CVE-2025-21885 as soon as they become available from trusted sources or Linux distribution vendors. 2. Temporarily disable the use_srq option in NVMe target configurations if patching cannot be immediately performed, to avoid triggering the vulnerability. 3. Monitor kernel logs for signs of divide errors or kernel panics related to bnxt_re or RDMA subsystems to detect potential exploitation or accidental triggering. 4. Conduct thorough testing of RDMA and NVMe target configurations in staging environments before deployment to production to identify any instability. 5. Maintain up-to-date backups and implement robust incident response procedures to quickly recover from potential denial of service events. 6. Engage with hardware vendors to ensure firmware and driver compatibility with patched kernel versions. 7. Limit access to systems using RDMA and NVMe targets to trusted administrators to reduce risk of accidental or malicious triggering of the vulnerability.

Need more detailed analysis?Get Pro

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: 682d9832c4522896dcbe8b04

Added to database: 5/21/2025, 9:09:06 AM

Last enriched: 6/30/2025, 10:24:34 AM

Last updated: 8/13/2025, 3:17:17 AM

Views: 21

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats