[CVE-2026-53348][LOW] ASoC: SDCA: fix NULL pointer dereference in sdca_dev_unregister_functions [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-53348
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: ASoC: SDCA: fix NULL pointer dereference in sdca_dev_unregister_functions [ Upstream
Commit: 9a4895059bb6a8505098a9f75de187fd15631fc8
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9a4895059bb6a8505098a9f75de187fd15631fc8
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53348
Analysis date: Wed, 01 Jul 2026 09:59:17 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A NULL pointer dereference in the ASoC SDCA SoundWire cleanup path can crash the kernel when partially registered function devices are unregistered after probe failure or cleanup races, but exploitation normally requires local device-management conditions and has DoS-only impact.

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

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

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-53348	LOW	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:N/I:N/A:H';**CWE-476;CWE-703;CWE-665;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A NULL pointer dereference can occur in the ASoC SDCA SoundWire cleanup path because sdca_dev_unregister_functions can call sdca_dev_unregister on NULL func_dev entries after partial registration failure or probe deferral cleanup. The crash occurs during device removal when the unregister path reaches device_del through an uninitialized function device pointer. For the CVSS the PR:L is used for the paranoid scenario because a reduced capability local service or delegated device management context might trigger driver probe cleanup or bind and unbind paths, while typical systems require administrator control. The issue is not network reachable and depends on local driver lifecycle conditions, firmware failure, or hardware probe behavior. Impact is denial of service via kernel oops only, with no supported evidence of information disclosure or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	DANGER NULLPTR INIT RACE HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The commit shows a concrete NULL pointer dereference reaching device_del() and producing a kernel oops.
* Requires admin/root/device-management control in typical deployments: -2. Reliable triggering normally requires driver bind/unbind, probe failure conditions, firmware setup problems, or SoundWire device cleanup paths, which are not ordinary unprivileged user actions.
* Rare AND difficult-to-reach subsystem/configuration: -1. The issue is in ASoC SDCA/SoundWire cleanup and was observed on a specific Panther Lake laptop platform with missing SOF firmware.

Conservative total is below zero, clamped to 0.

Paranoid signals:

* Reliable kernel crash / strong DoS: +1.
* Local delegated trigger possibility: +1. In a more cautious model, a reduced capability local service or delegated device-management environment might indirectly trigger driver reprobe, unbind, or cleanup.
* Requires privileged or semi-privileged device-management path: -1 to -2. This is not a normal unprivileged API and not network reachable.
* Rare hardware/probe-failure dependency: -1.

Paranoid total: 1.

No memory corruption bonus is applied. This is a NULL pointer dereference, not UAF, OOB write, double free, refcount takeover, type confusion, or attacker-controlled reuse. No LPE, confidentiality, or integrity signals are supported by the patch.

## 3. Reachability analysis

The likely trigger is local device lifecycle activity: failed SDCA function registration, probe deferral cleanup, missing firmware, SoundWire device removal, or driver unbind/reprobe. In normal deployments this is controlled by the kernel, firmware availability, hardware state, or administrator-level device management. There is no realistic network reachability.

Namespaces and containers usually do not help unless a container or service is explicitly granted device-management capabilities or access to relevant sysfs driver bind/unbind controls. The path is not broadly exposed as an unprivileged syscall or high-control kernel data-plane API.

Call-site confidence: high, because the patch and trace show the cleanup call chain and the exact NULL dereference path.

## 4. Severity interpretation

This behaves like a low-end Moderate or Low-like kernel DoS. The realistic impact is kernel oops during a narrow audio driver cleanup path. The theoretical bug class is not strong memory corruption. It is a NULL dereference caused by partially initialized cleanup state. There is no supported evidence of privilege escalation, information disclosure, arbitrary write, stale callback, object replacement, or attacker-controlled reclaim.

## 5. One-sentence report phrase

A NULL pointer dereference in the ASoC SDCA SoundWire cleanup path can crash the kernel when partially registered function devices are unregistered after probe failure or cleanup races, but exploitation normally requires local device-management conditions and has DoS-only impact.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be auto-closed for urgent security triage unless your product exposes SoundWire driver bind/unbind, firmware manipulation, or device reprobe controls to untrusted local users.

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

Patch: ASoC: SDCA: fix NULL pointer dereference in sdca_dev_unregister_functions [ Upstream
Commit: 9a4895059bb6a8505098a9f75de187fd15631fc8
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9a4895059bb6a8505098a9f75de187fd15631fc8

Changed files:
  sound/soc/sdca/sdca_function_device.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=9a4895059bb6a8505098a9f75de187fd15631fc8

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

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

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: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:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

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: 0
  Paranoid ActionableScore: 1

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