From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49671: RDMA/cm: Fix memory leak in ib_cm_insert_listen
Date: Wed, 26 Feb 2025 03:23:54 +0100 [thread overview]
Message-ID: <2025022624-CVE-2022-49671-62fb@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/cm: Fix memory leak in ib_cm_insert_listen
cm_alloc_id_priv() allocates resource for the cm_id_priv. When
cm_init_listen() fails it doesn't free it, leading to memory leak.
Add the missing error unwind.
The Linux kernel CVE team has assigned CVE-2022-49671 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit 98f67156a80f37db70ec64787020b1f9bc8aea8c and fixed in 5.10.129 with commit b0cab8b517aeaf2592c3479294f934209c41a26f
Issue introduced in 5.7 with commit 98f67156a80f37db70ec64787020b1f9bc8aea8c and fixed in 5.15.53 with commit 889000874c1204e47c7f2a4945db262a47e7efc9
Issue introduced in 5.7 with commit 98f67156a80f37db70ec64787020b1f9bc8aea8c and fixed in 5.18.10 with commit 2febf09a8a8ae4accf908f043f1bab1421056568
Issue introduced in 5.7 with commit 98f67156a80f37db70ec64787020b1f9bc8aea8c and fixed in 5.19 with commit 2990f223ffa7bb25422956b9f79f9176a5b38346
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-49671
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/core/cm.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/b0cab8b517aeaf2592c3479294f934209c41a26f
https://git.kernel.org/stable/c/889000874c1204e47c7f2a4945db262a47e7efc9
https://git.kernel.org/stable/c/2febf09a8a8ae4accf908f043f1bab1421056568
https://git.kernel.org/stable/c/2990f223ffa7bb25422956b9f79f9176a5b38346
reply other threads:[~2025-02-26 2:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022624-CVE-2022-49671-62fb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.