CVE-2022-49929: RDMA/rxe: Fix mr leak in RESPST_ERR_RNR
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
Security readout for executives and security teams
Plain-English summary
CVE-2022-49929 is a Linux kernel RDMA/rxe bug that can leak a memory-region reference in an error path. The public record does not provide a CVSS score or evidence of active exploitation. Business urgency is mainly for environments using software RoCE/RDMA or NVMe over RDMA on affected kernels.
Executive priority
Treat as a targeted infrastructure maintenance issue, not an internet-wide emergency. Patch promptly where RDMA/rxe is used in storage or high-performance computing, because kernel resource leaks can affect service reliability.
Technical view
In the RDMA rxe driver, rxe_recheck_mr() increments an MR reference count. In the RESPST_ERR_RNR path, the code failed to release it, causing a reference leak and kernel warning during cleanup. The referenced stable commits add the missing release.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the RDMA rxe software RoCE driver in use, especially RDMA/NVMe-RDMA workloads. Systems not using RDMA/rxe are less likely to be affected, but should still follow kernel vendor guidance.
Exploitation context
No KEV listing and no provided source reports active exploitation. The available evidence describes a kernel resource/reference leak and warning, not a public exploit chain. Practical impact is most likely reliability or availability risk in affected RDMA paths.
Researcher notes
The CVE metadata has unknown severity and limited affected-version detail. Analysis should focus on the RDMA/rxe RESPST_ERR_RNR path and whether downstream kernels backported the two stable commits. Do not assume exploitability beyond the documented reference leak.
Mitigation direction
Update to a Linux kernel or vendor package containing the referenced stable fixes.
Prioritize RDMA/rxe and NVMe-over-RDMA hosts in patch planning.
Check Linux distribution advisories for backported fixes and supported kernel versions.
If patching is delayed, follow vendor guidance for reducing RDMA/rxe exposure.
Validation and detection
Inventory Linux kernel versions on RDMA-capable systems.
Identify hosts using the rdma_rxe software RoCE driver.
Confirm installed kernels include the referenced stable fix commits or vendor backports.
Review kernel logs for RDMA/rxe cleanup warnings in affected environments.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49929 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 1, 2025, 14:11 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.