cve/published/2024/CVE-2024-50215.mbox

From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-50215: nvmet-auth: assign dh_key to NULL after kfree_sensitive

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

nvmet-auth: assign dh_key to NULL after kfree_sensitive

ctrl->dh_key might be used across multiple calls to nvmet_setup_dhgroup()
for the same controller. So it's better to nullify it after release on
error path in order to avoid double free later in nvmet_destroy_auth().

Found by Linux Verification Center (linuxtesting.org) with Svace.

The Linux kernel CVE team has assigned CVE-2024-50215 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.0 with commit 7a277c37d3522e9b2777d762bbbcecafae2b1f8d and fixed in 6.1.116 with commit c94e965f766321641ec38e4eece9ce8884543244
	Issue introduced in 6.0 with commit 7a277c37d3522e9b2777d762bbbcecafae2b1f8d and fixed in 6.6.60 with commit c60af16e1d6cc2237d58336546d6adfc067b6b8f
	Issue introduced in 6.0 with commit 7a277c37d3522e9b2777d762bbbcecafae2b1f8d and fixed in 6.11.7 with commit e61bd51e44409495d75847e9230736593e4c8710
	Issue introduced in 6.0 with commit 7a277c37d3522e9b2777d762bbbcecafae2b1f8d and fixed in 6.12 with commit d2f551b1f72b4c508ab9298419f6feadc3b5d791

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-50215
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/nvme/target/auth.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/c94e965f766321641ec38e4eece9ce8884543244
	https://git.kernel.org/stable/c/c60af16e1d6cc2237d58336546d6adfc067b6b8f
	https://git.kernel.org/stable/c/e61bd51e44409495d75847e9230736593e4c8710
	https://git.kernel.org/stable/c/d2f551b1f72b4c508ab9298419f6feadc3b5d791