CVE-2022-50850

scsi: ipr: Fix WARNING in ipr_init()

N/A
Published: December 30, 2025 at 12:15 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.34 ≤ v < 4.14.3032.6.34 ≤ v < 4.19.2702.6.34 ≤ v < 4.9.3372.6.34 ≤ v < 5.10.1632.6.34 ≤ v < 5.15.862.6.34 ≤ v < 5.4.2292.6.34 ≤ v < 6.0.162.6.34 ≤ v < 6.1.22.6.34 ≤ v < 6.22.6.34f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa
Vendor states this is fixed in 020b66023712b1cc42c6ab8b76e4ec13efe4a092 (fixed)
Vendor states this is fixed in 4399a8632e5f8f1f695d91d992c7d418fb451f07 (fixed)
Vendor states this is fixed in 5debd337f534b122f7c5eac6557a41b5636c9b51 (fixed)
Vendor states this is fixed in 8c739021b2022fbc40f71d3fa2e9162beef0c84a (fixed)
Vendor states this is fixed in e59da172059f05c594fda03a9e8a3a0e1f5116c0 (fixed)
Vendor states this is fixed in e6f108bffc3708ddcff72324f7d40dfcd0204894 (fixed)
Vendor states this is fixed in e965c4a60c1daa6e24355e35d78ca8e9f195196f (fixed)
Vendor states this is fixed in eccbec017c95b9b9ecd4c05c6f5234d1487c72cc (fixed)
Vendor states this is fixed in f4ba143b04a17559f2c85e18b47db117f40d8cf3 (fixed)
Vendor states this is fixed in 2.6.34 (unaffected)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card