[CVE-2026-72415][MODERATE REGULAR] ASoC: SDCA: Validate written enum value in ge_put_enum_double() [ Upstream

[CVE-2026-72415][MODERATE REGULAR] ASoC: SDCA: Validate written enum value in ge_put_enum_double() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72415
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: ASoC: SDCA: Validate written enum value in ge_put_enum_double() [ Upstream
Commit: 33387bf9bb6116a0429f823f8dab3accf8f8e09c
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=33387bf9bb6116a0429f823f8dab3accf8f8e09c
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72415
Analysis date: Sat, 15 Aug 2026 22:07:52 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline manual review recommended. Not an Important candidate based on current evidence
Manual review required: YES

Summary:
A local OOB read in the ASoC SDCA enum control write path allows an out-of-range user supplied enum index to read past the heap allocated values array, with realistic impact limited to local DoS or unintended control handling and no demonstrated privilege escalation primitive.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72415 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72415

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-72415	MODERATE	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:H';CWE-125;CWE-129;*CWE-20;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '6.6';DESCR 'An out of bounds read in the ASoC SDCA control path occurs because ge_put_enum_double uses a user supplied enum item index before checking it against e items. The index is passed to snd_soc_enum_item_to_val and can read past the heap allocated e values array when a local user writes an invalid enum value through the ALSA control interface. For the CVSS the PR:L is used because a local user or process needs access to the affected ALSA control device. The issue is not network reachable. Impact is at least a local denial of service or unintended control value handling. For the paranoid score, C:L I:L A:H is still defensible because the primitive is an out of bounds read from kernel heap memory, but the patch does not show an overwrite primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended. Not an Important candidate based on current evidence (with actual score 4)  SKIP CVE-2026-72415 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 812ff1baa764080ba37bb0729e0c23c0e869b542 YES  NO NO unknown 	MAYBE	OOB HARDWARE  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=4
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline manual review recommended. Not an Important candidate based on current evidence**

## 2. Signal breakdown

Triggered signals:

* Local unprivileged trigger: +1
  The affected path is an ALSA control write path. A local user or local process with access to the relevant sound control device may supply the enum value.

* Memory corruption, weak or indirect corruption candidate: +1
  The bug is an unchecked user-controlled array index into heap allocated `e->values[]`. This is an OOB read, not an OOB write.

* Availability impact realistic: +1
  A sufficiently out-of-range index may cause a kernel fault or otherwise invalid control handling. However, a reliable crash is not fully demonstrated by the patch.

Paranoid-only signal:

* Weak unintended integrity impact: +1
  The OOB read result is used as an enum value in a control update path, so unintended device or control state may be possible. This is not a proven arbitrary write or LPE primitive.

Deductions / non-awarded signals:

* No remote reachability: +0
  This is not network-triggerable.

* No strong LPE plausibility: +0
  The patch shows no reclaim, overwrite, type confusion, callback control, refcount abuse, or attacker-controlled object replacement.

* No strong memory corruption primitive: +0
  The primitive is read-only OOB from a heap array.

* No high-control API bonus: +0
  ALSA control configuration alone does not meet the high-control data-plane API threshold.

* Rare or device-specific exposure: considered but not applied as a hard penalty
  SDCA-specific ASoC hardware limits exposure, but the interface is still an ordinary local device interface when present.

Call-site confidence: medium. The immediate vulnerable use is shown, but broader downstream control effects depend on surrounding ASoC/SDCA control handling not fully included in the patch.

## 3. Reachability analysis

A local user or process that can write to the affected ALSA control can trigger the invalid enum index. In typical desktop or audio-enabled systems, access may be delegated to logged-in users through device permissions, audio groups, or session policy, so PR:L is more appropriate than PR:H for practical triage.

Containers usually do not get direct access to host sound controls unless the device node is passed through, so container reachability depends on device delegation. The path is not remotely reachable and does not involve packet parsing or network input.

The issue is hardware and driver dependent. It requires an affected SDCA ASoC control to exist, which limits broad exposure.

## 4. Severity interpretation

This behaves like a memory-safety Moderate issue rather than an Important-class vulnerability. The concrete primitive is a local OOB read from a heap allocated enum values array. The patch does not support arbitrary write, UAF reclaim, type confusion, privilege escalation, or information disclosure to userspace.

The conservative interpretation is local DoS or invalid control behavior. The paranoid interpretation allows limited integrity concern and stronger availability concern because the OOB value is consumed by a kernel control path, but this still remains below Important without a stronger exploit primitive.

## 5. One-sentence report phrase

A local OOB read in the ASoC SDCA enum control write path allows an out-of-range user supplied enum index to read past the heap allocated values array, with realistic impact limited to local DoS or unintended control handling and no demonstrated privilege escalation primitive.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: this is a kernel heap OOB read reachable from a local device control path. It is not strong enough for Important classification from the patch alone, but memory-safety issues in writable local kernel interfaces should not be auto-closed without checking downstream use of the read value.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: ASoC: SDCA: Validate written enum value in ge_put_enum_double() [ Upstream
Commit: 33387bf9bb6116a0429f823f8dab3accf8f8e09c
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=33387bf9bb6116a0429f823f8dab3accf8f8e09c

Changed files:
  sound/soc/sdca/sdca_asoc.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=33387bf9bb6116a0429f823f8dab3accf8f8e09c

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72415 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72415

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:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 6.6

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: 3
  Paranoid ActionableScore: 4

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).