CVE-2022-50850
Improper Cleanup in Linux ipr Driver Causes Kernel Warning
Publication date: 2025-12-30
Last updated on: 2025-12-30
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.1.0-rc1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the specific WARNING message related to ipr_init() in the system logs. You can use commands like 'dmesg | grep ipr' or 'journalctl -k | grep ipr' to look for the WARNING: 'notifier callback ipr_halt [ipr] already registered' or related messages indicating the issue.
Can you explain this vulnerability to me?
This vulnerability is related to the Linux kernel's ipr driver initialization function (ipr_init). When the pci_register_driver() call fails during initialization, ipr_init() does not call unregister_reboot_notifier(), which leads to a WARNING due to a notifier callback (ipr_halt) already being registered. The fix ensures that unregister_reboot_notifier() is called if pci_register_driver() fails, preventing this warning.
How can this vulnerability impact me? :
The impact of this vulnerability is primarily a warning message during the kernel module initialization process, indicating improper cleanup when pci_register_driver() fails. This could potentially lead to unstable or unexpected behavior during module loading, but no direct security impact or exploitation details are provided.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the ipr_init() function properly calls unregister_reboot_notifier() when pci_register_driver() fails, thus preventing the WARNING. Until then, monitoring for the warning messages and avoiding loading the ipr module if possible may reduce impact.