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: <2025123044-CVE-2022-50850-d6c0@gregkh>
Date: Tue, 30 Dec 2025 13:19:46 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50850: scsi: ipr: Fix WARNING in ipr_init()

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

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

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

scsi: ipr: Fix WARNING in ipr_init()

ipr_init() will not call unregister_reboot_notifier() when
pci_register_driver() fails, which causes a WARNING. Call
unregister_reboot_notifier() when pci_register_driver() fails.

notifier callback ipr_halt [ipr] already registered
WARNING: CPU: 3 PID: 299 at kernel/notifier.c:29
notifier_chain_register+0x16d/0x230
Modules linked in: ipr(+) xhci_pci_renesas xhci_hcd ehci_hcd usbcore
led_class gpu_sched drm_buddy video wmi drm_ttm_helper ttm
drm_display_helper drm_kms_helper drm drm_panel_orientation_quirks
agpgart cfbft
CPU: 3 PID: 299 Comm: modprobe Tainted: G        W
6.1.0-rc1-00190-g39508d23b672-dirty #332
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
RIP: 0010:notifier_chain_register+0x16d/0x230
Call Trace:
 <TASK>
 __blocking_notifier_chain_register+0x73/0xb0
 ipr_init+0x30/0x1000 [ipr]
 do_one_initcall+0xdb/0x480
 do_init_module+0x1cf/0x680
 load_module+0x6a50/0x70a0
 __do_sys_finit_module+0x12f/0x1c0
 do_syscall_64+0x3f/0x90
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

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


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

	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 4.9.337 with commit 020b66023712b1cc42c6ab8b76e4ec13efe4a092
	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 4.14.303 with commit e965c4a60c1daa6e24355e35d78ca8e9f195196f
	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 4.19.270 with commit 5debd337f534b122f7c5eac6557a41b5636c9b51
	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 5.4.229 with commit eccbec017c95b9b9ecd4c05c6f5234d1487c72cc
	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 5.10.163 with commit f4ba143b04a17559f2c85e18b47db117f40d8cf3
	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 5.15.86 with commit e59da172059f05c594fda03a9e8a3a0e1f5116c0
	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 6.0.16 with commit 8c739021b2022fbc40f71d3fa2e9162beef0c84a
	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 6.1.2 with commit 4399a8632e5f8f1f695d91d992c7d418fb451f07
	Issue introduced in 2.6.34 with commit f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and fixed in 6.2 with commit e6f108bffc3708ddcff72324f7d40dfcd0204894

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-50850
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/ipr.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/020b66023712b1cc42c6ab8b76e4ec13efe4a092
	https://git.kernel.org/stable/c/e965c4a60c1daa6e24355e35d78ca8e9f195196f
	https://git.kernel.org/stable/c/5debd337f534b122f7c5eac6557a41b5636c9b51
	https://git.kernel.org/stable/c/eccbec017c95b9b9ecd4c05c6f5234d1487c72cc
	https://git.kernel.org/stable/c/f4ba143b04a17559f2c85e18b47db117f40d8cf3
	https://git.kernel.org/stable/c/e59da172059f05c594fda03a9e8a3a0e1f5116c0
	https://git.kernel.org/stable/c/8c739021b2022fbc40f71d3fa2e9162beef0c84a
	https://git.kernel.org/stable/c/4399a8632e5f8f1f695d91d992c7d418fb451f07
	https://git.kernel.org/stable/c/e6f108bffc3708ddcff72324f7d40dfcd0204894

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ