From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-54458: scsi: ufs: bsg: Set bsg_queue to NULL after removal
Date: Wed, 26 Feb 2025 18:17:06 -0800 [thread overview]
Message-ID: <2025022602-CVE-2024-54458-75cd@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: bsg: Set bsg_queue to NULL after removal
Currently, this does not cause any issues, but I believe it is necessary to
set bsg_queue to NULL after removing it to prevent potential use-after-free
(UAF) access.
The Linux kernel CVE team has assigned CVE-2024-54458 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.129 with commit 5e7b6e44468c3242c21c2a8656d009fb3eb50a73
Fixed in 6.6.79 with commit 5f782d4741bf558def60df192b858b0efc6a5f0a
Fixed in 6.12.16 with commit 88a01e9c9ad40c075756ba93b47984461d4ff15d
Fixed in 6.13.4 with commit 9193bdc170cc23fe98aca71d1a63c0bf6e1e853b
Fixed in 6.14-rc1 with commit 1e95c798d8a7f70965f0f88d4657b682ff0ec75f
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-54458
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/core/ufs_bsg.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/5e7b6e44468c3242c21c2a8656d009fb3eb50a73
https://git.kernel.org/stable/c/5f782d4741bf558def60df192b858b0efc6a5f0a
https://git.kernel.org/stable/c/88a01e9c9ad40c075756ba93b47984461d4ff15d
https://git.kernel.org/stable/c/9193bdc170cc23fe98aca71d1a63c0bf6e1e853b
https://git.kernel.org/stable/c/1e95c798d8a7f70965f0f88d4657b682ff0ec75f
reply other threads:[~2025-02-27 2: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=2025022602-CVE-2024-54458-75cd@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.