linux-cve-announce - CVE-2022-50566: mtd: Fix device name leak when register device failed in add_mtd

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: <2025102207-CVE-2022-50566-9cd3@gregkh>
Date: Wed, 22 Oct 2025 15:24:14 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50566: mtd: Fix device name leak when register device failed in add_mtd_device()

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

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

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

mtd: Fix device name leak when register device failed in add_mtd_device()

There is a kmemleak when register device failed:
  unreferenced object 0xffff888101aab550 (size 8):
    comm "insmod", pid 3922, jiffies 4295277753 (age 925.408s)
    hex dump (first 8 bytes):
      6d 74 64 30 00 88 ff ff                          mtd0....
    backtrace:
      [<00000000bde26724>] __kmalloc_node_track_caller+0x4e/0x150
      [<000000003c32b416>] kvasprintf+0xb0/0x130
      [<000000001f7a8f15>] kobject_set_name_vargs+0x2f/0xb0
      [<000000006e781163>] dev_set_name+0xab/0xe0
      [<00000000e30d0c78>] add_mtd_device+0x4bb/0x700
      [<00000000f3d34de7>] mtd_device_parse_register+0x2ac/0x3f0
      [<00000000c0d88488>] 0xffffffffa0238457
      [<00000000b40d0922>] 0xffffffffa02a008f
      [<0000000023d17b9d>] do_one_initcall+0x87/0x2a0
      [<00000000770f6ca6>] do_init_module+0xdf/0x320
      [<000000007b6768fe>] load_module+0x2f98/0x3330
      [<00000000346bed5a>] __do_sys_finit_module+0x113/0x1b0
      [<00000000674c2290>] do_syscall_64+0x35/0x80
      [<000000004c6a8d97>] entry_SYSCALL_64_after_hwframe+0x46/0xb0

If register device failed, should call put_device() to give up the
reference.

The Linux kernel CVE team has assigned CVE-2022-50566 to this issue.


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

	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 4.9.337 with commit a75f45afa932bfb24a2603ebcea5efd2e7cdcfd6
	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 4.14.303 with commit 2302e2dc42b1f84f951c725ce742fc21c5a1e151
	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 4.19.270 with commit db07fe76df01f40cb897d6e9066b84e46957beb3
	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 5.4.229 with commit fa0d32ab8407d7481450c664fd0de64f2dae9489
	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 5.10.163 with commit 330bc5533e8a8ed69cb951d5a8edce9bddb9db21
	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 5.15.86 with commit 71212d73184845c944ef1b43f092e643e5bde003
	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 6.0.16 with commit 1b172fb05d6315ecec082fd7544a3390e96f0d7e
	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 6.1.2 with commit bcabe1dc2a344adbb3382930a23e273ba9382277
	Issue introduced in 2.6.30 with commit 1f24b5a8ecbb2a3c7080f418974d40e3ffedb221 and fixed in 6.2 with commit 895d68a39481a75c680aa421546931fb11942fa6

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-50566
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/mtd/mtdcore.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/a75f45afa932bfb24a2603ebcea5efd2e7cdcfd6
	https://git.kernel.org/stable/c/2302e2dc42b1f84f951c725ce742fc21c5a1e151
	https://git.kernel.org/stable/c/db07fe76df01f40cb897d6e9066b84e46957beb3
	https://git.kernel.org/stable/c/fa0d32ab8407d7481450c664fd0de64f2dae9489
	https://git.kernel.org/stable/c/330bc5533e8a8ed69cb951d5a8edce9bddb9db21
	https://git.kernel.org/stable/c/71212d73184845c944ef1b43f092e643e5bde003
	https://git.kernel.org/stable/c/1b172fb05d6315ecec082fd7544a3390e96f0d7e
	https://git.kernel.org/stable/c/bcabe1dc2a344adbb3382930a23e273ba9382277
	https://git.kernel.org/stable/c/895d68a39481a75c680aa421546931fb11942fa6