[CVE-2026-53052][MODERATE REGULAR] ASoC: qcom: qdsp6: topology: check widget type before accessing data [ Upstream

[CVE-2026-53052][MODERATE REGULAR] ASoC: qcom: qdsp6: topology: check widget type before accessing data [ Upstream

[AL-KERNEL]

CVE: CVE-2026-53052
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: ASoC: qcom: qdsp6: topology: check widget type before accessing data [ Upstream
Commit: 8e8cd78b6000c9d19db249a5a68287158f288ef3
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8e8cd78b6000c9d19db249a5a68287158f288ef3
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53052
Analysis date: Fri, 26 Jun 2026 12:19:50 -0400
ActionableScore: 4
ActionableScore lower bound: 1
Actionable bucket: Borderline manual review recommended / ordinary Moderate unless delegated local reachability is confirmed
Manual review required: YES

Summary:
ASoC qcom qdsp6 topology unload may interpret virtual widget private data as an audioreach module before checking the widget type, causing incorrect memory access or NULL dereference with likely local DoS impact and only weak privilege escalation concern.

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

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

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-53052	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';CWE-843;**CWE-476;CWE-125;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.8';DESCR 'ASoC qcom qdsp6 topology unload can access dobj private as an audioreach_module before checking whether the widget is a virtual mixer. For a virtual widget the same private pointer may actually refer to snd_ar_control, so the early mod container read is a type confusion style invalid memory access and can also become a NULL pointer dereference if the private pointer is absent. For the CVSS the PR:L is used for the paranoid view because a local untrusted process may be able to reach this path through delegated audio service or device management contexts, while the common base case is closer to PR:H. The issue is not network reachable. Impact is at least local denial of service via kernel warning or crash, with limited confidentiality or integrity impact only in the paranoid view because the primitive is an invalid read rather than an arbitrary write.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended / ordinary Moderate unless delegated local reachability is confirmed (with actual score 3)  SKIP CVE-2026-53052  SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	SIMPLEFIX HARDWARE  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=4
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 4
* Final recommended bucket: **Borderline manual review recommended / ordinary Moderate unless delegated local reachability is confirmed**::

## 2. Signal breakdown

Conservative signals:

* Weak/indirect corruption candidate: +1. The bug is a type confusion style invalid object interpretation where `dobj->private` may be treated as `struct audioreach_module` before confirming the widget type.
* Reliable kernel crash / strong DoS: +1. A NULL `dobj->private` or invalid layout can lead to incorrect memory access or NULL dereference during widget unload.
* Privileged kernel/device-management memory corruption path: +1. The affected path is inside an ASoC Qualcomm qdsp6 topology unload path, a trusted kernel driver management context.
* Requires admin/root/device-management privileges in typical deployments: -2. Reliable triggering usually requires control over audio topology loading/unloading, driver lifecycle, or privileged sound subsystem management.
* Net result conservative: 1.

Paranoid signals:

* Local unprivileged or reduced-privilege trigger possibility: +1. Some systems may expose audio topology or device-management operations through a delegated audio service, container device passthrough, or reduced-privilege service account.
* Weak/indirect corruption candidate: +1. The primitive is invalid struct interpretation, not a proven arbitrary write or UAF.
* Reliable kernel crash / strong DoS: +1. The patch directly prevents incorrect memory access before widget type validation.
* Privileged kernel/device-management memory corruption path: +1. The bug occurs in a kernel driver topology teardown path.
* No strong LPE primitive added. There is no demonstrated reclaim, overwrite, UAF, controlled target, or attacker-controlled payload.
* Net result paranoid: 4.

## 3. Reachability analysis

The bug is local and not network reachable. In normal deployments, triggering appears to require privileged control over Qualcomm ASoC qdsp6 AudioReach topology objects, widget unload, or driver/device lifecycle operations. This is not a broad default server exposure and is relevant mainly to systems using the affected Qualcomm audio stack. Namespaces or containers generally do not make this reachable unless audio devices or topology management are explicitly delegated. A reduced-privilege audio service could make PR:L plausible for paranoid triage, but typical host deployments are closer to PR:H.

## 4. Severity interpretation

This behaves like a low-to-borderline Moderate kernel driver bug. The theoretical concern is type confusion style invalid memory access in kernel space, but the patch only shows an early read of the wrong private object and a possible NULL dereference. There is no clear UAF, OOB write, arbitrary write, refcount takeover, or page-cache style ownership violation. Realistic impact is most likely local DoS during audio topology unload. Privilege escalation is not strongly supported by the patch context, but manual review is reasonable because incorrect object interpretation occurs in kernel driver code.

## 5. One-sentence report phrase

ASoC qcom qdsp6 topology unload may interpret virtual widget private data as an audioreach module before checking the widget type, causing incorrect memory access or NULL dereference with likely local DoS impact and only weak privilege escalation concern.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the issue is not strong enough for automatic Important classification, but it involves kernel-space type confusion style invalid object interpretation in a privileged device-management path, and delegated audio-service reachability should be checked before auto-closing.

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

Patch: ASoC: qcom: qdsp6: topology: check widget type before accessing data [ Upstream
Commit: 8e8cd78b6000c9d19db249a5a68287158f288ef3
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8e8cd78b6000c9d19db249a5a68287158f288ef3

Changed files:
  sound/soc/qcom/qdsp6/topology.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=8e8cd78b6000c9d19db249a5a68287158f288ef3

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

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

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

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