Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocal access to i.MX fsl_micfil audio device
-
ExploitIssue unbalanced PCM hw_free/repeated hw_params
-
ExecutionTrigger MCLK enable/disable reference imbalance
-
ImpactWARN splat and ungateable clock
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Resource release
|
| Exploitation Conditions | Requires a kernel built with the NXP i.MX fsl_micfil ASoC driver (digital PDM microphone interface) present and in use, and local access to the corresponding ALSA PCM device to drive the state machine into the unbalanced paths - specifically triggering hw_free() without a preceding hw_params(), or calling hw_params() multiple times from the SETUP state. Limiting factors: this affects only NXP i.MX platforms that enable fsl_micfil (not generic x86/server kernels), local device access is required, and the observed result is a kernel WARN() and a leaked MCLK enable reference leaving the clock ungateable - there is no described memory-corruption or code-execution primitive. |
| Impact | This is a resource-management defect (CWE-404) in the NXP i.MX fsl_micfil ASoC driver: hw_params() enables MCLK unconditionally and hw_free() disables it unconditionally, so the unguarded paths produce an "already disabled" WARN() or leak an enable reference that leaves the clock ungateable. The input CVSS of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) appears inflated for the described behavior: a clock enable/disable imbalance that triggers a WARN splat and prevents clock gating has at most a minor local availability/power-management impact, not high confidentiality and integrity impact - this is the standard conservatively-high score the kernel CVE process auto-assigns, and it should be treated with skepticism. The supporting signals all point to low real-world risk: EPSS is 0.17% (5th percentile), there is no CISA KEV listing, and no exploit or PoC reference is present (the only references are the kernel.org stable fix commits and the NVD page). The vuln.today 'this_week' priority reflects routine stable-tree patch hygiene rather than active threat. Net: this is a low-priority, defense-in-depth kernel fix for a specific embedded audio driver, not an urgent broadly-exploitable vulnerability; the headline CVSS overstates the practical impact - verify the C/I/A rating against the described WARN/clock-leak behavior before prioritizing on score alone. |
| Exploit ScenarioDerived | On an NXP i.MX device whose kernel includes the fsl_micfil PDM-microphone driver, a local user with access to the audio PCM device drives the ALSA state machine so that hw_free() runs without a matching hw_params(), or calls hw_params() repeatedly from the SETUP state. This triggers a kernel WARN() or leaks an MCLK enable reference, leaving the clock permanently ungated (a noisy log splat and a minor power/availability nuisance). No public exploit or PoC is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
The NXP i.MX fsl_micfil ASoC driver in the Linux kernel mismanages the MCLK microphone clock: hw_params() enables it and hw_free() disables it without guarding against unbalanced calls, so ALSA PCM operations can produce an "already disabled" kernel WARN() or leak an enable reference that leaves the clock permanently ungated. Only systems built with this digital PDM microphone driver and exposed to the corresponding local ALSA PCM device are affected; the practical consequence is a warning and a resource leak, with no memory corruption or code execution primitive described. No public exploit code has been identified at time of analysis, and the issue is assessed as low availability impact requiring local access (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L); a vendor patch is available per the kernel stable commits.
RemediationAI
Apply the upstream fix by updating to a kernel release that includes the balanced mclk enable/disable change, drawn from the 7.3-rc3 line, the 6.18.53 stable release, or the 7.2.7 stable release containing commits 470db2026a435b79f7ecb4d65523ea16a99d55d8, d3dbccfe6afa7b9a6a7ed65cfaa76a47fa050a56 and fa1bbe3534499dd89d3b0b941d6dd4ddb70c31b5 respectively; distribution kernels should be updated to a build carrying the corresponding backport. If updating immediately is not possible, the driver can be omitted from the kernel configuration (do not build or load snd_soc_fsl_micfil) on systems that do not need the i.MX PDM microphone interface, at the cost of losing microphone capture capability on those platforms. Restricting access to the ALSA PCM device nodes to trusted local users reduces the chance of triggering the unbalanced state machine paths, though it does not remove the defect. Kernel stable references are listed at https://git.kernel.org/stable/c/470db2026a435b79f7ecb4d65523ea16a99d55d8, https://git.kernel.org/stable/c/d3dbccfe6afa7b9a6a7ed65cfaa76a47fa050a56 and https://git.kernel.org/stable/c/fa1bbe3534499dd89d3b0b941d6dd4ddb70c31b5.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the ALSA System-on-Chip (ASoC) driver fsl_micfil, which drives the NXP i.MX digital PDM microphone interface and manages a master clock (MCLK) for the microphone subsystem. The PCM core does not guarantee a 1:1 pairing between the hw_params() and hw_free() callbacks: hw_free() may run without a preceding hw_params(), and hw_params() may be invoked repeatedly while the stream remains in the SETUP state. Because the driver enables MCLK unconditionally in hw_params() and disables it unconditionally in hw_free(), the first case triggers a clock-framework "already disabled" WARN() and the second leaks an enable reference, leaving the clock ungated. The root cause is classified as CWE-404 (Improper Resource Shutdown or Release), i.e. unbalanced resource accounting rather than memory-safety corruption. The upstream fix guards both sides with the driver's existing mclk_flag, mirroring the mclk_streams-based bookkeeping already used in fsl_sai.c. The trigger is exercised through local access to the ALSA PCM device; no privilege escalation, information disclosure or code-execution primitive is described in the available sources.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local access to the audio PCM device (PR:L, AV:L) triggers a WARN and an ungateable clock - a minor availability/power nuisance (A:L), with no confidentiality or integrity impact.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
In the Linux kernel, the following vulnerability has been resolved:
ASoC: fsl_micfil: balance mclk enable/disable
hw_params() enables mclk unconditionally and hw_free() disables it unconditionally, but the PCM core does not guarantee 1:1 pairing: hw_free() can run without hw_params(), and hw_params() can be called multiple times from the SETUP state. This triggers an "already disabled" WARN() in the first case and leaks an enable reference in the second, leaving the clock ungateable.
Guard both sides with the existing mclk_flag, as fsl_sai.c does with mclk_streams.
Executive ViewAI
The NXP i.MX fsl_micfil audio driver has a clock management flaw that can cause system warnings and a resource leak, potentially degrading audio functionality on affected embedded Linux systems. Only devices using this specific microphone driver with local ALSA access are impacted, which likely includes certain industrial or IoT products. Leadership should prioritize patching to prevent operational disruptions in audio-dependent applications.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
EUVD-2026-86923
GHSA-c37f-rq9m-6c5r
NVD
CVE.org
EPSS
Exploit-DB