During device initialization the driver marks the audio interface as active but neglects to enable a required clock, causing the system to record the clock as unpowered. When a runtime suspend occurs the Linux runtime power‑management system attempts to turn the clock off again, leading to a double‑disable. This triggers a warning in the kernel log and may prevent the I2S interface from operating correctly, potentially interrupting audio processing or other functions that rely on the clock. The issue does not expose any direct data leakage or code execution path. The problem is purely a software bug affecting clock state management.

The vulnerability exists in the Linux kernel’s Android Sound Architecture (ASoC) driver for Samsung I2S devices. All kernel versions that include the old probe implementation and lack the patch that enables the op_clk during probe are affected. The issue was observed on the Exynos5250 (Arndale), where both the iis and rclk_src clocks share the same gate.

No CVSS score is provided and the EPSS score is not available; the vulnerability is not listed in the CISA KEV catalog. Because the flaw is a mis‑enabled clock rather than an exploitable privilege escalation or code execution path, the risk is low and it is unlikely to be targeted by attackers. An attacker would first need to wait for the device to encounter the double‑disable condition, which would only signal a warning and cause limited service disruption. The vulnerability does not create a clear attack vector. The current best assessment is that it poses a low‑severity, low‑exploitability risk.