From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49376: scsi: sd: Fix potential NULL pointer dereference
Date: Wed, 26 Feb 2025 03:10:50 +0100 [thread overview]
Message-ID: <2025022646-CVE-2022-49376-9ec1@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: sd: Fix potential NULL pointer dereference
If sd_probe() sees an early error before sdkp->device is initialized,
sd_zbc_release_disk() is called. This causes a NULL pointer dereference
when sd_is_zoned() is called inside that function. Avoid this by removing
the call to sd_zbc_release_disk() in sd_probe() error path.
This change is safe and does not result in zone information memory leakage
because the zone information for a zoned disk is allocated only when
sd_revalidate_disk() is called, at which point sdkp->disk_dev is fully set,
resulting in sd_disk_release() being called when needed to cleanup a disk
zone information using sd_zbc_release_disk().
The Linux kernel CVE team has assigned CVE-2022-49376 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.10 with commit 89d9475610771b5e5fe1879075f0fc9ba6e3755f and fixed in 5.10.122 with commit c1f0187025905e9981000d44a92e159468b561a8
Issue introduced in 4.10 with commit 89d9475610771b5e5fe1879075f0fc9ba6e3755f and fixed in 5.15.47 with commit 0fcb0b131cc90c8f523a293d84c58d0c7273c96f
Issue introduced in 4.10 with commit 89d9475610771b5e5fe1879075f0fc9ba6e3755f and fixed in 5.17.15 with commit 78f8e96df06e2d04d82d4071c299b59d28744f47
Issue introduced in 4.10 with commit 89d9475610771b5e5fe1879075f0fc9ba6e3755f and fixed in 5.18.4 with commit 3733439593ad12f7b54ae35c273ea6f15d692de3
Issue introduced in 4.10 with commit 89d9475610771b5e5fe1879075f0fc9ba6e3755f and fixed in 5.19 with commit 05fbde3a77a4f1d62e4c4428f384288c1f1a0be5
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-49376
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/sd.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/c1f0187025905e9981000d44a92e159468b561a8
https://git.kernel.org/stable/c/0fcb0b131cc90c8f523a293d84c58d0c7273c96f
https://git.kernel.org/stable/c/78f8e96df06e2d04d82d4071c299b59d28744f47
https://git.kernel.org/stable/c/3733439593ad12f7b54ae35c273ea6f15d692de3
https://git.kernel.org/stable/c/05fbde3a77a4f1d62e4c4428f384288c1f1a0be5
reply other threads:[~2025-02-26 2:13 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=2025022646-CVE-2022-49376-9ec1@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.