From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-99089][LOW] ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM [ Upstream Date: Mon, 26 Oct 2026 22:08:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-99089 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 0 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 2c64c30d493d82d5edc95811cede0083e1195822 List-Id: CVE: CVE-2026-99089 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM [ Upstream Commit: 2c64c30d493d82d5edc95811cede0083e1195822 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2c64c30d493d82d5edc95811cede0083e1195822 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99089 Analysis date: Mon, 26 Oct 2026 22:08:12 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: Samsung I2S probe failed to acquire an `op_clk` enable reference, causing the first runtime suspend to warn about disabling an already-disabled shared clock gate. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-99089 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99089 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-99089 LOW https://www.kernelcve.org/list/?q=CVE-2026-99089 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT LOW AEGIS_AS=0 LEGACY=LOW RESULT=SAME (final reconciliation agrees; DECISION: both LOW) Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';CWE-675;CWE-404;*CWE-664;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '3.3';DESCR 'The samsung i2s probe path entered the runtime PM active state lacking a matching enable reference for op_clk. On systems where op_clk and the main i2s clock resolve to the same gate, the first runtime suspend disables that gate twice and reaches clk_core_disable with an already disabled clock, producing a kernel warning. The bug class is a logic and resource state imbalance with no invalid memory access, UAF, OOB access, or write primitive. Availability impact is low because the demonstrated result is a warning and possible audio disruption rather than a normal configuration kernel crash. The issue is local and hardware specific with no direct network reachability. For the CVSS the PR:L value is used because a meaningful attacker driven trigger would normally require local access to exercise the audio device and its runtime PM transitions. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 3.3 and the production ActionableScore returned 0 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. No severity changing production threshold or specialist override was recorded. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. The independent weaker Aegis shadow evaluated CVSS 2.5 and ActionableScore 0 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was LOW. The shadow agreed with the final production impact and aggregation did not change that impact. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0) MAYBE INIT WARNONLY HARDWARE - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES RequiresHostUID0=UNKNOWN AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw base score: 0. * Conservative score: 0; no floor or cap applies. * Raw paranoid score: 0. * Paranoid score: 0; no technically supported stronger consequence. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +0 warning/state imbalance: probe leaves `op_clk` without a matching enable reference, while runtime suspend disables it. * +0 availability: the demonstrated result is `clk_core_disable()` warning that the shared clock gate is already disabled; host crash or strong DoS is not shown. * +0 corruption: no OOB access, UAF, invalid free, stale pointer, heap overwrite, or attacker-controlled write is present. * +0 resource leak: the patch balances clock enable/disable references but does not show a persistent leaked resource. * No authorization signal: no access-control guard or DENY-to-ALLOW transition exists. * No B5-R or B3-PENDING mechanics: there is neither a retry-accumulated OOB write nor a shared-backing write. * No hardware penalty applied: the affected Exynos clock topology is hardware-specific, but physical attacker access or genuinely rare hardware is not established. 3. Reachability analysis The faulty first runtime suspend can occur through the PM workqueue after probe, potentially during boot. The evidence does not establish an attacker-controlled trigger, required credentials, host UID 0, or a namespace-scoped operation. Local audio-device activity might influence runtime PM transitions, but complete below-host-admin reachability is unproven. No network path, race, prior delegated setup, or attacker-instantiated object is shown. 4. Primitive and severity reading The exact defect is a clock prepare/enable reference imbalance. The fix enables `op_clk` during probe and disables it during removal, matching runtime-PM state. This is neither active structured-state corruption nor a lifetime violation. The shown effect is a warning and possible device/audio malfunction; kernel panic, memory corruption, privilege escalation, and protected-resource impact are unsupported. Therefore `PrimitiveClass=NONE`, no Important candidate exists, and automatic downgrade is safe. 5. One-sentence report phrase Samsung I2S probe failed to acquire an `op_clk` enable reference, causing the first runtime suspend to warn about disabling an already-disabled shared clock gate. 6. Manual review advice NO MANUAL CHECK NEEDED The patch shows a contained clock-state accounting error without a security primitive. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM [ Upstream Commit: 2c64c30d493d82d5edc95811cede0083e1195822 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2c64c30d493d82d5edc95811cede0083e1195822 Changed files: drivers/clk/clk.c sound/soc/samsung/i2s.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2c64c30d493d82d5edc95811cede0083e1195822 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-99089 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99089 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS score: 3.3 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: unknown Paranoid ActionableScore: 0 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).