From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-48725: RDMA/siw: Fix refcounting leak in siw_create_qp()
Date: Thu, 20 Jun 2024 13:16:05 +0200 [thread overview]
Message-ID: <2024062058-CVE-2022-48725-aba3@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/siw: Fix refcounting leak in siw_create_qp()
The atomic_inc() needs to be paired with an atomic_dec() on the error
path.
The Linux kernel CVE team has assigned CVE-2022-48725 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 514aee660df4 and fixed in 5.15.22 with commit 2989ba9532ba
Issue introduced in 5.15 with commit 514aee660df4 and fixed in 5.16.8 with commit fa3b844a5084
Issue introduced in 5.15 with commit 514aee660df4 and fixed in 5.17 with commit a75badebfdc0
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-48725
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/sw/siw/siw_verbs.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/2989ba9532babac66e79997ccff73c015b69700c
https://git.kernel.org/stable/c/fa3b844a50845c817660146c27c0fc29b08d3116
https://git.kernel.org/stable/c/a75badebfdc0b3823054bedf112edb54d6357c75
reply other threads:[~2024-06-20 11:18 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=2024062058-CVE-2022-48725-aba3@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.