linux-cve-announce - CVE-2022-50340: media: vimc: Fix wrong function called when vimc

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: <2025091638-CVE-2022-50340-693e@gregkh>
Date: Tue, 16 Sep 2025 18:11:36 +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-50340: media: vimc: Fix wrong function called when vimc_init() fails

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

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

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

media: vimc: Fix wrong function called when vimc_init() fails

In vimc_init(), when platform_driver_register(&vimc_pdrv) fails,
platform_driver_unregister(&vimc_pdrv) is wrongly called rather than
platform_device_unregister(&vimc_pdev), which causes kernel warning:

 Unexpected driver unregister!
 WARNING: CPU: 1 PID: 14517 at drivers/base/driver.c:270 driver_unregister+0x8f/0xb0
 RIP: 0010:driver_unregister+0x8f/0xb0
 Call Trace:
  <TASK>
  vimc_init+0x7d/0x1000 [vimc]
  do_one_initcall+0xd0/0x4e0
  do_init_module+0x1cf/0x6b0
  load_module+0x65c2/0x7820

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


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

	Issue introduced in 4.13 with commit 4a29b70907496aa9da79112ec31cf9cf2b972c3f and fixed in 5.10.163 with commit 14d85b600bb1f6f8ef61fa8fc1907e2e623d8350
	Issue introduced in 4.13 with commit 4a29b70907496aa9da79112ec31cf9cf2b972c3f and fixed in 5.15.86 with commit 9c9ff35d68691aaea85b2e93763772e23930b3a3
	Issue introduced in 4.13 with commit 4a29b70907496aa9da79112ec31cf9cf2b972c3f and fixed in 6.0.16 with commit 681ac2902039d9b497b3ae18fdc204314979e61e
	Issue introduced in 4.13 with commit 4a29b70907496aa9da79112ec31cf9cf2b972c3f and fixed in 6.1.2 with commit f38df8984ef1b45ba23888d0e232cc21a95bd04b
	Issue introduced in 4.13 with commit 4a29b70907496aa9da79112ec31cf9cf2b972c3f and fixed in 6.2 with commit f74d3f326d1d5b8951ce263c59a121ecfa65e7c0

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-50340
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/media/test-drivers/vimc/vimc-core.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/14d85b600bb1f6f8ef61fa8fc1907e2e623d8350
	https://git.kernel.org/stable/c/9c9ff35d68691aaea85b2e93763772e23930b3a3
	https://git.kernel.org/stable/c/681ac2902039d9b497b3ae18fdc204314979e61e
	https://git.kernel.org/stable/c/f38df8984ef1b45ba23888d0e232cc21a95bd04b
	https://git.kernel.org/stable/c/f74d3f326d1d5b8951ce263c59a121ecfa65e7c0