From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-90068][MODERATE REGULAR] ASoC: dapm: Fix off-by-one check on the second enum channel [ Upstream Date: Fri, 18 Sep 2026 07:42:03 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-90068 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 3 X-AL-KERNEL-ActionableScore-Lower: 2 X-AL-KERNEL-Commit: 57ab955bde747327fb2042516ae1b7192c30e881 List-Id: CVE: CVE-2026-90068 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: ASoC: dapm: Fix off-by-one check on the second enum channel [ Upstream Commit: 57ab955bde747327fb2042516ae1b7192c30e881 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=57ab955bde747327fb2042516ae1b7192c30e881 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90068 Analysis date: Fri, 18 Sep 2026 07:42:03 -0400 ActionableScore: 3 ActionableScore lower bound: 2 Actionable bucket: Borderline / manual review recommended Manual review required: YES Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-90068 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90068 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: MODERATE REGULAR Manual review required: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-90068 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-90068 CHECK WITH IMPACT FROM ORIG NN 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:L/I:L/A:N';CWE-193;CWE-125;*CWE-20;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N';BEST CVSS score: '4.4';DESCR 'An off-by-one bounds check in snd_soc_dapm_put_enum_double allows the second enum channel to accept an index equal to the number of items. That index can reach snd_soc_enum_item_to_val and read one element past the end of an enum value table. A local user with access to the affected ALSA control can trigger this by writing an out of range enum value on systems using a vulnerable codec setup such as the adav80x value table case. For the CVSS the PR:L value is used because triggering requires a local user or process that can access the sound control device, but does not require full administrator privileges in typical desktop or audio group configurations. The issue is not network reachable. Impact is mainly a local integrity policy or device state impact, with a conservative C:L in the paranoid score because the primitive is an out of bounds kernel read.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3) YES SIMPLEFIX HARDWARE INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=3 ActionableScoreLower=2 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=NO NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 2 * Conservative score: 2. No floor or cap applied. * Raw paranoid score: 3 * Paranoid score: 3. No floor or cap applied. * Final recommended bucket: **Borderline / manual review recommended**:: 2. Signal breakdown Conservative signals: * +1 Local below-host-admin trigger. A local user or process with access to the affected ALSA control can write the out-of-range enum value. * +1 Weak invalid index / limited OOB read. The off-by-one check lets item[1] == e->items reach snd_soc_enum_item_to_val(), causing a one-element OOB read from e->values. Paranoid additional signal: * +1 Limited device-state integrity concern. The OOB-read value is used to build the value written through the control path, so a wrong codec/device state is plausible, but this is not evidence of kernel memory corruption or privilege escalation. Non-awarded material signals: * RealUAF not awarded. No stale lifetime, free, put, or post-lifetime object use is established. * Strong corruption not awarded. No OOB write, arbitrary write, controlled reclaim, type confusion, callback influence, or refcount/lifetime takeover is shown. * Confidentiality not awarded. The OOB-read value is not shown to be copied to userspace, network, logs containing sensitive data, or another attacker-visible disclosure sink. * Reliable kernel crash not awarded. The patch shows a one-element read past a value table, not a demonstrated panic or fatal fault. * Remote reachability not awarded. This is an ALSA local control path, not packet or network input. * ImportantCandidate not awarded. The primitive is a constrained local OOB read with at most limited device-state effect and no established exploitation leverage beyond that. * Extra availability not awarded. No independent persistent DoS or host-wide failure is demonstrated. 3. Reachability analysis The evaluated attacker is a local user or local process that can access the relevant ALSA control device. In typical desktop or audio-group configurations this may be below host administrator, so HostAdminRequired=NO for this assessed path. The issue is not namespace-scoped and no user namespace or container capability is relevant to the complete trigger chain. The vulnerable path requires an affected ASoC codec/control configuration. The commit notes that only adav80x pairs a value table with two shifts and that its second channel reports two values. This makes real exposure narrower than a generic ALSA issue. CONFIG_SND_CTL_INPUT_VALIDATION would catch the bad input, but it defaults off according to the supplied context. No race or special timing is required. 4. Primitive and severity interpretation The exact primitive is an off-by-one bounds check on the second enum channel in snd_soc_dapm_put_enum_double(). item[1] equal to e->items is accepted and then used as an index into e->values by snd_soc_enum_item_to_val(), producing a one-element kernel OOB read. This is not an active structured UAF and not fixed stale storage. It is a bounded read-only array over-index with possible incorrect codec/device state programming. There is no concrete repeated release/refcount operation, no first lifetime operation that may free an object, and no second lifetime mutation. PrimitiveClass=CLASS_C because the demonstrated behavior is a constrained invalid read / invalid state without an independently useful corruption primitive. The demonstrated consequence is local misuse of an ALSA control causing an internal OOB read and possibly incorrect device state. Speculative consequences such as kernel information disclosure or privilege escalation are not supported by the supplied patch context. ImportantCandidate=NO because no Class A primitive and no strong Class B lifetime/corruption primitive exists. AutoDowngradeAllowed=YES because the issue lacks UAF, ownership violation, security-boundary bypass, controlled corruption, demonstrated disclosure, or LPE evidence. Operational severity is low to borderline moderate, with manual review mainly needed to confirm affected codec exposure and device permissions. 5. One-sentence report phrase A local user with access to an affected ALSA ASoC control can trigger a one-element out-of-bounds read in snd_soc_dapm_put_enum_double by writing an invalid second enum value, with impact limited to possible incorrect device state and no demonstrated kernel disclosure, crash, or privilege escalation. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Manual review is recommended to confirm whether affected adav80x-style controls are exposed on the target product and whether normal users can write them. The primitive itself is limited and does not justify Important severity from the supplied evidence. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ASoC: dapm: Fix off-by-one check on the second enum channel [ Upstream Commit: 57ab955bde747327fb2042516ae1b7192c30e881 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=57ab955bde747327fb2042516ae1b7192c30e881 Changed files: sound/soc/soc-dapm.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=57ab955bde747327fb2042516ae1b7192c30e881 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-90068 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90068 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:L/PR:L/UI:N/S:U/C:N/I:L/A:N The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N The Best / paranoid CVSS score: 4.4 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: 2 Paranoid ActionableScore: 3 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: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR 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).