linux-cve-announce - CVE-2020-36790: nvmet: fix a memory leak

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025050110-CVE-2020-36790-c8e2@gregkh>
Date: Thu,  1 May 2025 16:09:11 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2020-36790: nvmet: fix a memory leak

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

nvmet: fix a memory leak

We forgot to free new_model_number

The Linux kernel CVE team has assigned CVE-2020-36790 to this issue.


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

	Issue introduced in 5.7 with commit 013b7ebe5a0d70e2a02fd225174595e79c591b3e and fixed in 5.8.6 with commit 227064b2ca9e62270ed445665ae849c73f0dfb2c
	Issue introduced in 5.7 with commit 013b7ebe5a0d70e2a02fd225174595e79c591b3e and fixed in 5.9 with commit 382fee1a8b623e2546a3e15e80517389e0e0673e

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-2020-36790
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/configfs.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/227064b2ca9e62270ed445665ae849c73f0dfb2c
	https://git.kernel.org/stable/c/382fee1a8b623e2546a3e15e80517389e0e0673e