CVE-2022-50011
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
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 manifests as a warning during the Venus driver probe in the Linux kernel, specifically a WARN triggered at drivers/opp/core.c:2471 in dev_pm_opp_set_config. Detection involves checking system logs for this warning message. You can use commands like 'dmesg | grep dev_pm_opp_set_config' or 'journalctl -k | grep dev_pm_opp_set_config' to find occurrences of this warning in kernel logs.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by re-ordering the code related to the OPP core so that all configuration options are provided before the OPP table is added. Immediate mitigation involves updating the Linux kernel to a version that includes this fix (post 5.19.0-rc8-next-20220728). Until then, monitoring for the warning and avoiding use of affected kernel versions is recommended.
How can this vulnerability impact me? :
The vulnerability causes a warning during the Venus driver probe, which may lead to the failure of the video codec driver initialization (as indicated by the probe failure with error -16). This could impact the functionality of devices relying on this driver, potentially causing issues with video codec operations on affected hardware.
Can you explain this vulnerability to me?
This vulnerability is a warning triggered during the probe of the Venus driver in the Linux kernel, specifically related to the Operating Performance Points (OPP) core. The issue occurs because the OPP core expects all configuration options to be set before the OPP table is added, but the code did not follow this order, causing a warning during driver initialization. The fix involved re-ordering the code to ensure configurations are set before adding the OPP table.