CVE-2023-53866

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-09. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

December 9, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

ASoC: soc-compress: Reposition and add pcm_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aa9ff6a4955fdba02b54fbc4386db876603703b7
generic

ASoC: soc-compress: Reposition and add pcm_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a9942cbdb7c3f41452f7bc4a9ff9f0b45eb3651
generic

ASoC: soc-compress: Reposition and add pcm_mutex - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37a3eb6054d17676ce2a0bb5dd1fbf7733ecfa7d

Vendor Advisories for CVE-2023-53866(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 6.1.16—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

(refreshed 19× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-08-05 19:15 UTCEPSS rescore
  2. 2026-08-05 19:15 UTCEPSS rescore
  3. 2026-08-05 10:15 UTCEG score recompute
  4. 2026-08-05 10:15 UTCVendor advisory
  5. 2026-08-05 10:15 UTCGHSA enrichment
  6. 2026-08-04 10:51 UTCEG score recompute
  7. 2026-08-04 10:51 UTCVendor advisory
  8. 2026-08-04 10:51 UTCGHSA enrichment
  9. 2026-08-04 10:36 UTCEPSS rescore
  10. 2026-08-04 09:26 UTCEG score recompute▲ 7.80
  11. 2026-08-04 09:26 UTCVendor advisory
  12. 2026-08-04 09:26 UTCGHSA enrichment
  13. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-08-03 10:34 UTCEPSS rescore
  15. 2026-08-02 02:25 UTCEPSS rescore
  16. 2026-08-02 02:25 UTCEPSS rescore
  17. 2026-08-01 04:14 UTCEPSS rescore
  18. 2026-07-30 16:26 UTCEPSS rescore
  19. 2026-07-30 01:29 UTCEPSS rescore
  20. 2026-07-28 15:34 UTCEPSS rescore
  21. 2026-07-28 15:34 UTCEPSS rescore
  22. 2026-07-27 05:39 UTCOSV refresh
  23. 2026-07-26 14:53 UTCEPSS rescore
  24. 2026-07-25 14:16 UTCEPSS rescore
  25. 2026-07-24 14:16 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 14:16 UTCEPSS rescore
  2. 2026-07-23 02:30 UTCEG score recompute
  3. 2026-07-22 23:16 UTCEG score recompute
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-21 15:23 UTCEPSS rescore
  7. 2026-07-20 17:06 UTCEPSS rescore
  8. 2026-07-19 14:30 UTCEPSS rescore
  9. 2026-07-19 14:29 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-19 02:27 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-18 10:03 UTCEPSS rescore
  14. 2026-07-16 17:01 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 01:59 UTCEPSS rescore
  17. 2026-07-15 01:59 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 22:28 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-12 05:45 UTCEPSS rescore
  22. 2026-07-12 05:45 UTCEPSS rescore
  23. 2026-07-11 08:26 UTCEPSS rescore
  24. 2026-07-10 00:15 UTCOSV refresh
  25. 2026-07-09 19:08 UTCEPSS rescore
  26. 2026-07-08 15:13 UTCEPSS rescore
  27. 2026-07-07 13:45 UTCEPSS rescore
  28. 2026-07-07 13:44 UTCEPSS rescore
  29. 2026-07-06 16:26 UTCEPSS rescore
  30. 2026-07-06 16:26 UTCEPSS rescore
  31. 2026-07-06 02:22 UTCEPSS rescore
  32. 2026-07-06 02:22 UTCEPSS rescore
  33. 2026-07-05 02:29 UTCEPSS rescore
  34. 2026-07-04 06:29 UTCEPSS rescore
  35. 2026-07-01 15:05 UTCEPSS rescore
  36. 2026-06-30 23:21 UTCEPSS rescore
  37. 2026-06-30 23:21 UTCEPSS rescore
  38. 2026-06-29 14:05 UTCEPSS rescore
  39. 2026-06-28 14:06 UTCEPSS rescore
  40. 2026-06-28 14:06 UTCEPSS rescore
  41. 2026-06-28 04:55 UTCEPSS rescore
  42. 2026-06-27 03:07 UTCEPSS rescore
  43. 2026-06-25 13:48 UTCEPSS rescore
  44. 2026-06-25 13:48 UTCEPSS rescore
  45. 2026-06-24 14:04 UTCEPSS rescore
  46. 2026-06-24 14:04 UTCEPSS rescore
  47. 2026-06-23 21:31 UTCEPSS rescore
  48. 2026-06-23 21:31 UTCEPSS rescore
  49. 2026-06-22 14:24 UTCEPSS rescore
  50. 2026-06-22 14:24 UTCEPSS rescore
  51. 2026-06-21 14:55 UTCEPSS rescore
  52. 2026-06-21 14:55 UTCEPSS rescore
  53. 2026-06-21 10:31 UTCOSV refresh
  54. 2026-06-21 01:58 UTCEPSS rescore
  55. 2026-06-21 01:58 UTCEPSS rescore
  56. 2026-06-19 19:24 UTCEPSS rescore
  57. 2026-06-19 19:24 UTCEPSS rescore
  58. 2026-06-18 17:51 UTCEPSS rescore
  59. 2026-06-17 17:51 UTCEPSS rescore
  60. 2026-06-16 17:51 UTCEPSS rescore
  61. 2026-06-16 17:51 UTCEPSS rescore
  62. 2026-06-15 17:47 UTCEPSS rescore
  63. 2026-06-14 23:16 UTCEPSS rescore
  64. 2026-06-13 22:59 UTCEPSS rescore
  65. 2026-06-13 22:59 UTCEPSS rescore
  66. 2026-06-12 23:11 UTCEPSS rescore
  67. 2026-06-11 13:59 UTCEPSS rescore
  68. 2026-06-10 22:17 UTCEPSS rescore
  69. 2026-06-10 13:21 UTCEPSS rescore
  70. 2026-06-08 14:16 UTCEPSS rescore
  71. 2026-06-08 14:16 UTCEPSS rescore
  72. 2026-06-07 15:24 UTCEPSS rescore
  73. 2026-06-07 15:24 UTCEPSS rescore
  74. 2026-06-06 13:46 UTCEPSS rescore
  75. 2026-06-06 13:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-53866?
CVE-2023-53866 is a high vulnerability published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-compress: Reposition and add pcm_mutex If paniconwarn 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…
When was CVE-2023-53866 disclosed?
CVE-2023-53866 was first published in the National Vulnerability Database on December 9, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53866 actively exploited?
CVE-2023-53866 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.4% of all scored CVEs.
What is the CVSS score of CVE-2023-53866?
CVE-2023-53866 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-53866?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53866, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-53866

Explore →

Is Your Infrastructure Affected by CVE-2023-53866?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs