linux-cve-announce - CVE-2022-49206: RDMA/mlx5: Fix memory leak in error flow for subscribe event routine

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025022618-CVE-2022-49206-51a6@gregkh>
Date: Wed, 26 Feb 2025 02:56:51 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49206: RDMA/mlx5: Fix memory leak in error flow for subscribe event routine

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

RDMA/mlx5: Fix memory leak in error flow for subscribe event routine

In case the second xa_insert() fails, the obj_event is not released.  Fix
the error unwind flow to free that memory to avoid a memory leak.

The Linux kernel CVE team has assigned CVE-2022-49206 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.3 with commit 7597385371425febdaa8c6a1da3625d4ffff16f5 and fixed in 5.4.189 with commit 0174a89663a5ef83617da15bf24c0af2f62b6c7f
	Issue introduced in 5.3 with commit 7597385371425febdaa8c6a1da3625d4ffff16f5 and fixed in 5.10.110 with commit c98d903ff9e79c210beddea4e6bc15ac38e25aa5
	Issue introduced in 5.3 with commit 7597385371425febdaa8c6a1da3625d4ffff16f5 and fixed in 5.15.33 with commit 8dd392e352d3269938fea32061a74655a613f929
	Issue introduced in 5.3 with commit 7597385371425febdaa8c6a1da3625d4ffff16f5 and fixed in 5.16.19 with commit d66498507801fd9a20307a15a0814a0a016c3cde
	Issue introduced in 5.3 with commit 7597385371425febdaa8c6a1da3625d4ffff16f5 and fixed in 5.17.2 with commit 414b4e8738484379f18d6c4e780787c80dbf8a2c
	Issue introduced in 5.3 with commit 7597385371425febdaa8c6a1da3625d4ffff16f5 and fixed in 5.18 with commit 087f9c3f2309ed183f7e4b85ae57121d8663224d

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-49206
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/infiniband/hw/mlx5/devx.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/0174a89663a5ef83617da15bf24c0af2f62b6c7f
	https://git.kernel.org/stable/c/c98d903ff9e79c210beddea4e6bc15ac38e25aa5
	https://git.kernel.org/stable/c/8dd392e352d3269938fea32061a74655a613f929
	https://git.kernel.org/stable/c/d66498507801fd9a20307a15a0814a0a016c3cde
	https://git.kernel.org/stable/c/414b4e8738484379f18d6c4e780787c80dbf8a2c
	https://git.kernel.org/stable/c/087f9c3f2309ed183f7e4b85ae57121d8663224d