CVE-2022-49929: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix mr leak in RESPST_ERR_RNR rxe_recheck_mr() will increase mr's ref_cnt, so we should call rxe_put(mr) to drop mr's ref_cnt in RESPST_ERR_RNR to avoid below warning: WARNING: CPU: 0 PID: 4156 at drivers/infiniband/sw/rxe/rxe_pool.c:259 __rxe_cleanup+0x1df/0x240 [rdma_rxe] ... Call Trace: rxe_dereg_mr+0x4c/0x60 [rdma_rxe] ib_dereg_mr_user+0xa8/0x200 [ib_core] ib_mr_pool_destroy+0x77/0xb0 [ib_core] nvme_rdma_destroy_queue_ib+0x89/0x240 [nvme_rdma] nvme_rdma_free_queue+0x40/0x50 [nvme_rdma] nvme_rdma_teardown_io_queues.part.0+0xc3/0x120 [nvme_rdma] nvme_rdma_error_recovery_work+0x4d/0xf0 [nvme_rdma] process_one_work+0x582/0xa40 ? pwq_dec_nr_in_flight+0x100/0x100 ? rwlock_bug.part.0+0x60/0x60 worker_thread+0x2a9/0x700 ? process_one_work+0xa40/0xa40 kthread+0x168/0x1a0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30
AI Analysis
Technical Summary
CVE-2022-49929 is a vulnerability identified in the Linux kernel's RDMA (Remote Direct Memory Access) subsystem, specifically within the rxe driver component. The issue relates to a memory reference counting leak in the function rxe_recheck_mr() when handling the RESPST_ERR_RNR state. The vulnerability arises because rxe_recheck_mr() increments the memory region's (mr) reference count (ref_cnt), but under the RESPST_ERR_RNR condition, the corresponding decrement (via rxe_put(mr)) was missing. This leads to a reference count leak, which can cause resource exhaustion or memory leaks within the kernel. The warning logs indicate that this leak manifests as a kernel warning during cleanup operations in rxe_pool.c, potentially destabilizing the RDMA driver and related subsystems. The affected code paths include deregistration and destruction of memory regions and NVMe RDMA queue teardown and error recovery routines. Although no known exploits are reported in the wild, the vulnerability could degrade system stability or cause denial of service in environments relying on RDMA over Ethernet (rxe) for high-performance networking. This is particularly relevant for Linux systems running kernel versions containing the affected commit (hash 8a1a0be894da0d06bfbb496cc2dc3057fa83e103). The fix involves ensuring that the reference count is properly decremented to prevent leaks and warnings.
Potential Impact
For European organizations, especially those operating data centers, HPC clusters, or storage systems leveraging RDMA for low-latency, high-throughput networking, this vulnerability could lead to kernel instability or denial of service due to resource leaks. Organizations using NVMe over RDMA for storage acceleration may experience degraded performance or unexpected failures during error recovery or queue teardown operations. While the vulnerability does not directly enable code execution or privilege escalation, the resulting kernel warnings and resource leaks can cause system crashes or degraded availability, impacting critical infrastructure and services. This is particularly significant for sectors such as finance, telecommunications, research institutions, and cloud service providers in Europe that rely on Linux-based RDMA implementations for performance-sensitive workloads. The absence of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future exploitation or accidental service disruption.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernel to a version that includes the patch fixing CVE-2022-49929. Since the issue is in the RDMA rxe driver, organizations should audit their use of RDMA over Ethernet and NVMe RDMA features and consider temporarily disabling these features if they are not critical to operations. Kernel upgrades should be tested in staging environments to ensure compatibility with existing RDMA workloads. Monitoring kernel logs for warnings related to rxe_pool.c and memory region reference counts can help detect attempts to trigger the issue. Additionally, organizations should implement robust resource monitoring and alerting to identify abnormal memory usage patterns that may indicate leaks. For environments where immediate patching is not feasible, applying kernel live patching solutions (if supported) or isolating vulnerable hosts from critical workloads can reduce exposure. Finally, maintaining up-to-date backups and recovery plans is essential to mitigate potential service disruptions caused by this vulnerability.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Switzerland, Italy
CVE-2022-49929: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix mr leak in RESPST_ERR_RNR rxe_recheck_mr() will increase mr's ref_cnt, so we should call rxe_put(mr) to drop mr's ref_cnt in RESPST_ERR_RNR to avoid below warning: WARNING: CPU: 0 PID: 4156 at drivers/infiniband/sw/rxe/rxe_pool.c:259 __rxe_cleanup+0x1df/0x240 [rdma_rxe] ... Call Trace: rxe_dereg_mr+0x4c/0x60 [rdma_rxe] ib_dereg_mr_user+0xa8/0x200 [ib_core] ib_mr_pool_destroy+0x77/0xb0 [ib_core] nvme_rdma_destroy_queue_ib+0x89/0x240 [nvme_rdma] nvme_rdma_free_queue+0x40/0x50 [nvme_rdma] nvme_rdma_teardown_io_queues.part.0+0xc3/0x120 [nvme_rdma] nvme_rdma_error_recovery_work+0x4d/0xf0 [nvme_rdma] process_one_work+0x582/0xa40 ? pwq_dec_nr_in_flight+0x100/0x100 ? rwlock_bug.part.0+0x60/0x60 worker_thread+0x2a9/0x700 ? process_one_work+0xa40/0xa40 kthread+0x168/0x1a0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30
AI-Powered Analysis
Technical Analysis
CVE-2022-49929 is a vulnerability identified in the Linux kernel's RDMA (Remote Direct Memory Access) subsystem, specifically within the rxe driver component. The issue relates to a memory reference counting leak in the function rxe_recheck_mr() when handling the RESPST_ERR_RNR state. The vulnerability arises because rxe_recheck_mr() increments the memory region's (mr) reference count (ref_cnt), but under the RESPST_ERR_RNR condition, the corresponding decrement (via rxe_put(mr)) was missing. This leads to a reference count leak, which can cause resource exhaustion or memory leaks within the kernel. The warning logs indicate that this leak manifests as a kernel warning during cleanup operations in rxe_pool.c, potentially destabilizing the RDMA driver and related subsystems. The affected code paths include deregistration and destruction of memory regions and NVMe RDMA queue teardown and error recovery routines. Although no known exploits are reported in the wild, the vulnerability could degrade system stability or cause denial of service in environments relying on RDMA over Ethernet (rxe) for high-performance networking. This is particularly relevant for Linux systems running kernel versions containing the affected commit (hash 8a1a0be894da0d06bfbb496cc2dc3057fa83e103). The fix involves ensuring that the reference count is properly decremented to prevent leaks and warnings.
Potential Impact
For European organizations, especially those operating data centers, HPC clusters, or storage systems leveraging RDMA for low-latency, high-throughput networking, this vulnerability could lead to kernel instability or denial of service due to resource leaks. Organizations using NVMe over RDMA for storage acceleration may experience degraded performance or unexpected failures during error recovery or queue teardown operations. While the vulnerability does not directly enable code execution or privilege escalation, the resulting kernel warnings and resource leaks can cause system crashes or degraded availability, impacting critical infrastructure and services. This is particularly significant for sectors such as finance, telecommunications, research institutions, and cloud service providers in Europe that rely on Linux-based RDMA implementations for performance-sensitive workloads. The absence of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future exploitation or accidental service disruption.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernel to a version that includes the patch fixing CVE-2022-49929. Since the issue is in the RDMA rxe driver, organizations should audit their use of RDMA over Ethernet and NVMe RDMA features and consider temporarily disabling these features if they are not critical to operations. Kernel upgrades should be tested in staging environments to ensure compatibility with existing RDMA workloads. Monitoring kernel logs for warnings related to rxe_pool.c and memory region reference counts can help detect attempts to trigger the issue. Additionally, organizations should implement robust resource monitoring and alerting to identify abnormal memory usage patterns that may indicate leaks. For environments where immediate patching is not feasible, applying kernel live patching solutions (if supported) or isolating vulnerable hosts from critical workloads can reduce exposure. Finally, maintaining up-to-date backups and recovery plans is essential to mitigate potential service disruptions caused by this vulnerability.
Affected Countries
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
- 2025-05-01T14:05:17.254Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982bc4522896dcbe4092
Added to database: 5/21/2025, 9:08:59 AM
Last enriched: 6/29/2025, 8:42:57 PM
Last updated: 8/1/2025, 1:51:15 AM
Views: 13
Related Threats
CVE-2025-9094: Improper Neutralization of Special Elements Used in a Template Engine in ThingsBoard
MediumCVE-2025-9093: Improper Export of Android Application Components in BuzzFeed App
MediumCVE-2025-9091: Hard-coded Credentials in Tenda AC20
LowCVE-2025-9090: Command Injection in Tenda AC20
MediumCVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowActions
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.