From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-57872: scsi: ufs: pltfrm: Dellocate HBA during ufshcd_pltfrm_remove()
Date: Sat, 11 Jan 2025 15:31:06 +0100 [thread overview]
Message-ID: <2025011104-CVE-2024-57872-28ee@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: pltfrm: Dellocate HBA during ufshcd_pltfrm_remove()
This will ensure that the scsi host is cleaned up properly using
scsi_host_dev_release(). Otherwise, it may lead to memory leaks.
The Linux kernel CVE team has assigned CVE-2024-57872 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.10 with commit 03b1781aa978aab345b5a85d8596f8615281ba89 and fixed in 6.12.5 with commit cd188519d2467ab4c2141587b0551ba030abff0e
Issue introduced in 3.10 with commit 03b1781aa978aab345b5a85d8596f8615281ba89 and fixed in 6.13-rc2 with commit 897df60c16d54ad515a3d0887edab5c63da06d1f
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-2024-57872
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/ufs/host/ufshcd-pltfrm.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/cd188519d2467ab4c2141587b0551ba030abff0e
https://git.kernel.org/stable/c/897df60c16d54ad515a3d0887edab5c63da06d1f
reply other threads:[~2025-01-11 14:31 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=2025011104-CVE-2024-57872-28ee@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.