CVE-2023-53842
BaseFortify
Publication date: 2025-12-09
Last updated on: 2025-12-09
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves resource leaks in the Linux kernel's ASoC codec driver wcd-mbhc-v2. Specifically, MBHC resources are not properly released when the component probe fails or when the component is removed. This improper handling can cause failures when the sound card tries to re-probe the codec component, leading to errors such as failed instantiation of the sound card and failed initialization of MBHC interrupts.
How can this vulnerability impact me? :
This vulnerability can cause failures in the sound subsystem of the Linux kernel, particularly affecting the instantiation and initialization of sound cards using the affected codec. This may result in audio devices not functioning correctly or failing to initialize, potentially impacting systems relying on these audio components.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring system logs for specific error messages related to the wcd-mbhc-v2 codec component. Look for errors such as 'failed to instantiate card -517', 'Flags mismatch irq', 'Failed to request mbhc interrupts -16', 'mbhc initialization failed', and 'error at snd_soc_component_probe on audio-codec: -16'. Commands like 'dmesg | grep -i mbhc' or 'journalctl -k | grep -i mbhc' can help identify these errors in kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the resource leak issue in the wcd-mbhc-v2 codec component has been fixed. Ensuring that the MBHC resources are properly released on component probe failure and removal will prevent the errors and failures described. If an update is not immediately possible, monitoring and restarting the affected sound components or the system may temporarily alleviate the issue.