https://vulnerability.circl.lu/sightings/feed 2026-05-06T09:46:47.147188+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/5e029a79-9119-4597-bf8c-2da6d43d3bb9/export 2026-05-06T09:46:47.565994+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "5e029a79-9119-4597-bf8c-2da6d43d3bb9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-49929", "type": "seen", "source": "https://t.me/cvedetector/24240", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2022-49929 - \"RDMA rxe Memory Reference Count Leak Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2022-49929 \nPublished : May 1, 2025, 3:16 p.m. | 1\u00a0hour, 9\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nRDMA/rxe: Fix mr leak in RESPST_ERR_RNR \n \nrxe_recheck_mr() will increase mr's ref_cnt, so we should call rxe_put(mr) \nto drop mr's ref_cnt in RESPST_ERR_RNR to avoid below warning: \n \n WARNING: CPU: 0 PID: 4156 at drivers/infiniband/sw/rxe/rxe_pool.c:259 __rxe_cleanup+0x1df/0x240 [rdma_rxe] \n... \n Call Trace: \n rxe_dereg_mr+0x4c/0x60 [rdma_rxe] \n ib_dereg_mr_user+0xa8/0x200 [ib_core] \n ib_mr_pool_destroy+0x77/0xb0 [ib_core] \n nvme_rdma_destroy_queue_ib+0x89/0x240 [nvme_rdma] \n nvme_rdma_free_queue+0x40/0x50 [nvme_rdma] \n nvme_rdma_teardown_io_queues.part.0+0xc3/0x120 [nvme_rdma] \n nvme_rdma_error_recovery_work+0x4d/0xf0 [nvme_rdma] \n process_one_work+0x582/0xa40 \n ? pwq_dec_nr_in_flight+0x100/0x100 \n ? rwlock_bug.part.0+0x60/0x60 \n worker_thread+0x2a9/0x700 \n ? process_one_work+0xa40/0xa40 \n kthread+0x168/0x1a0 \n ? kthread_complete_and_exit+0x20/0x20 \n ret_from_fork+0x22/0x30 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"01 May 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T19:01:29.000000Z"} 2025-05-01T19:01:29+00:00