CVE-2022-50029
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-13
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) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| 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
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's clock framework for the Qualcomm IPQ8074 platform. When USB sleep clocks are disabled, the kernel attempts to disable the sleep clock source as well, but this sleep clock source cannot be disabled. Trying to disable it causes the kernel to produce errors and warnings, potentially leading to system instability or crashes. The fix involves marking the sleep clock as critical so the kernel does not attempt to disable it.
How can this vulnerability impact me? :
This vulnerability can cause kernel errors and warnings related to clock management, which may lead to system instability or crashes on affected devices using the Qualcomm IPQ8074 platform. This could impact device reliability and availability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the kernel logs for specific error messages related to the clock framework trying to disable the sleep clock source. Look for messages containing 'gcc_sleep_clk_src status stuck at 'on'' and warnings from clk_branch_wait. You can use the command 'dmesg | grep gcc_sleep_clk_src' or 'journalctl -k | grep gcc_sleep_clk_src' to find these logs.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the fix is applied. The fix involves adding the CLK_IS_CRITICAL flag to the clock so that the kernel will not attempt to disable the sleep clock source, preventing the error from occurring.