CVE-2022-50698
Unknown Unknown - Not Provided
Error Handling Flaw in Linux ASoC da7219 clk Registration

Publication date: 2025-12-24

Last updated on: 2025-12-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: ASoC: da7219: Fix an error handling path in da7219_register_dai_clks() If clk_hw_register() fails, the corresponding clk should not be unregistered. To handle errors from loops, clean up partial iterations before doing the goto. So add a clk_hw_unregister(). Then use a while (--i >= 0) loop in the unwind section.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-24
Last Modified
2025-12-24
Generated
2026-05-27
AI Q&A
2025-12-24
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is related to the Linux kernel's ASoC da7219 driver. Specifically, it involves an error handling issue in the function da7219_register_dai_clks(). If the function clk_hw_register() fails, the code incorrectly attempts to unregister the corresponding clock, which should not happen. The fix involves properly cleaning up partial iterations in error loops and correctly unregistering clocks using a while loop to avoid improper handling.


How can this vulnerability impact me? :

If this vulnerability is exploited or triggered, it could lead to improper error handling in the Linux kernel's audio subsystem, potentially causing instability or crashes related to clock registration in the da7219 driver. This could affect system reliability or audio functionality on affected devices.


What immediate steps should I take to mitigate this vulnerability?

Apply the patch or update to the Linux kernel version that includes the fix for the da7219_register_dai_clks() error handling path. This involves ensuring that the clk_hw_unregister() is properly called on failure to prevent improper clock unregistration. Since this is a kernel-level fix, updating the kernel to the fixed version is the recommended mitigation.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart