CVE-2022-50850 — scsi: ipr: Fix WARNING in ipr_init()
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
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < 020b66023712b1cc42c6ab8b76e4ec13efe4a092≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < e965c4a60c1daa6e24355e35d78ca8e9f195196f≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < 5debd337f534b122f7c5eac6557a41b5636c9b51≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < eccbec017c95b9b9ecd4c05c6f5234d1487c72cc≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < f4ba143b04a17559f2c85e18b47db117f40d8cf3≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < e59da172059f05c594fda03a9e8a3a0e1f5116c0≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < 8c739021b2022fbc40f71d3fa2e9162beef0c84a≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < 4399a8632e5f8f1f695d91d992c7d418fb451f07 and 2 more≥ f72919ec2bbbe1c42cdda7857a96c0c40e1d78aa and < e6f108bffc3708ddcff72324f7d40dfcd0204894version 2.6.34 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.23%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- git.kernel.org/stable/c/5debd337f534b122f7c5eac6557a41b5636c9b51
- git.kernel.org/stable/c/f4ba143b04a17559f2c85e18b47db117f40d8cf3
- git.kernel.org/stable/c/eccbec017c95b9b9ecd4c05c6f5234d1487c72cc
- git.kernel.org/stable/c/8c739021b2022fbc40f71d3fa2e9162beef0c84a
- git.kernel.org/stable/c/4399a8632e5f8f1f695d91d992c7d418fb451f07
- git.kernel.org/stable/c/e6f108bffc3708ddcff72324f7d40dfcd0204894
- git.kernel.org/stable/c/e59da172059f05c594fda03a9e8a3a0e1f5116c0
- git.kernel.org/stable/c/e965c4a60c1daa6e24355e35d78ca8e9f195196f
- git.kernel.org/stable/c/020b66023712b1cc42c6ab8b76e4ec13efe4a092
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-50850 is "scsi: ipr: Fix WARNING in ipr_init()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.