CVE-2023-53866
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-09

Last updated on: 2025-12-09

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-compress: Reposition and add pcm_mutex If panic_on_warn is set and compress stream(DPCM) is started, then kernel panic occurred because card->pcm_mutex isn't held appropriately. In the following functions, warning were issued at this line "snd_soc_dpcm_mutex_assert_held". static int dpcm_be_connect(struct snd_soc_pcm_runtime *fe, struct snd_soc_pcm_runtime *be, int stream) { ... snd_soc_dpcm_mutex_assert_held(fe); ... } void dpcm_be_disconnect(struct snd_soc_pcm_runtime *fe, int stream) { ... snd_soc_dpcm_mutex_assert_held(fe); ... } void snd_soc_runtime_action(struct snd_soc_pcm_runtime *rtd, int stream, int action) { ... snd_soc_dpcm_mutex_assert_held(rtd); ... } int dpcm_dapm_stream_event(struct snd_soc_pcm_runtime *fe, int dir, int event) { ... snd_soc_dpcm_mutex_assert_held(fe); ... } These functions are called by soc_compr_set_params_fe, soc_compr_open_fe and soc_compr_free_fe without pcm_mutex locking. And this is call stack. [ 414.527841][ T2179] pc : dpcm_process_paths+0x5a4/0x750 [ 414.527848][ T2179] lr : dpcm_process_paths+0x37c/0x750 [ 414.527945][ T2179] Call trace: [ 414.527949][ T2179] dpcm_process_paths+0x5a4/0x750 [ 414.527955][ T2179] soc_compr_open_fe+0xb0/0x2cc [ 414.527972][ T2179] snd_compr_open+0x180/0x248 [ 414.527981][ T2179] snd_open+0x15c/0x194 [ 414.528003][ T2179] chrdev_open+0x1b0/0x220 [ 414.528023][ T2179] do_dentry_open+0x30c/0x594 [ 414.528045][ T2179] vfs_open+0x34/0x44 [ 414.528053][ T2179] path_openat+0x914/0xb08 [ 414.528062][ T2179] do_filp_open+0xc0/0x170 [ 414.528068][ T2179] do_sys_openat2+0x94/0x18c [ 414.528076][ T2179] __arm64_sys_openat+0x78/0xa4 [ 414.528084][ T2179] invoke_syscall+0x48/0x10c [ 414.528094][ T2179] el0_svc_common+0xbc/0x104 [ 414.528099][ T2179] do_el0_svc+0x34/0xd8 [ 414.528103][ T2179] el0_svc+0x34/0xc4 [ 414.528125][ T2179] el0t_64_sync_handler+0x8c/0xfc [ 414.528133][ T2179] el0t_64_sync+0x1a0/0x1a4 [ 414.528142][ T2179] Kernel panic - not syncing: panic_on_warn set ... So, I reposition and add pcm_mutex to resolve lockdep error.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-09
Last Modified
2025-12-09
Generated
2026-06-16
AI Q&A
2025-12-09
EPSS Evaluated
2026-06-14
NVD
CVE-2023-53866
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 Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel's ASoC soc-compress component occurs because the pcm_mutex lock is not properly held when starting a compress stream (DPCM). If the kernel is configured with panic_on_warn set, this improper locking leads to a kernel panic. The issue arises in several functions that call snd_soc_dpcm_mutex_assert_held without holding the pcm_mutex, causing warnings and ultimately a panic when the compress stream is started. The fix involved repositioning and adding pcm_mutex locking to prevent this panic.

Impact Analysis

If this vulnerability is triggered, it can cause the Linux kernel to panic and stop functioning, leading to a system crash. This can result in downtime, loss of data, and disruption of services on systems using the affected kernel component when compress streams are started with panic_on_warn enabled.

Detection Guidance

This vulnerability can be detected by monitoring the system kernel logs for warnings related to snd_soc_dpcm_mutex_assert_held and kernel panics triggered when panic_on_warn is set. Specifically, look for log entries showing call traces involving soc_compr_open_fe, dpcm_process_paths, and related functions. Commands such as 'dmesg | grep snd_soc_dpcm_mutex_assert_held' or 'journalctl -k | grep panic_on_warn' can help identify these issues.

Mitigation Strategies

To mitigate this vulnerability immediately, update the Linux kernel to a version where the pcm_mutex locking has been properly added and repositioned in the soc-compress component, as described in the fix. If updating is not immediately possible, consider disabling panic_on_warn to prevent kernel panic on warnings related to this issue, though this is a temporary measure and not a full fix.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2023-53866. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart