From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49121: scsi: pm8001: Fix tag leaks on error
Date: Wed, 26 Feb 2025 02:55:26 +0100 [thread overview]
Message-ID: <2025022604-CVE-2022-49121-9a82@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: pm8001: Fix tag leaks on error
In pm8001_chip_set_dev_state_req(), pm8001_chip_fw_flash_update_req(),
pm80xx_chip_phy_ctl_req() and pm8001_chip_reg_dev_req() add missing calls
to pm8001_tag_free() to free the allocated tag when pm8001_mpi_build_cmd()
fails.
Similarly, in pm8001_exec_internal_task_abort(), if the chip ->task_abort
method fails, the tag allocated for the abort request task must be
freed. Add the missing call to pm8001_tag_free().
The Linux kernel CVE team has assigned CVE-2022-49121 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.111 with commit a0bb65eadbf942024226241d9d99fed17168940b
Fixed in 5.15.34 with commit 43c617eefab7077d69f5989ad3e2a273da1d728b
Fixed in 5.16.20 with commit bdc74815f1c39905054b7d47399e0260b201b14d
Fixed in 5.17.3 with commit 9cc72bcc1c096ed42c91646f130d4b4191580a4c
Fixed in 5.18 with commit 4c8f04b1905cd4b776d0b720463c091545478ef7
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-49121
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/scsi/pm8001/pm8001_hwi.c
drivers/scsi/pm8001/pm8001_sas.c
drivers/scsi/pm8001/pm80xx_hwi.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/a0bb65eadbf942024226241d9d99fed17168940b
https://git.kernel.org/stable/c/43c617eefab7077d69f5989ad3e2a273da1d728b
https://git.kernel.org/stable/c/bdc74815f1c39905054b7d47399e0260b201b14d
https://git.kernel.org/stable/c/9cc72bcc1c096ed42c91646f130d4b4191580a4c
https://git.kernel.org/stable/c/4c8f04b1905cd4b776d0b720463c091545478ef7
reply other threads:[~2025-02-26 1:58 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=2025022604-CVE-2022-49121-9a82@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.