dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53350

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 6.1.176 / 6.6.143 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: ASoC: wm_adsp: Fix NULL dereference when removing firmware controls In wm_adsp_control_remove() check that the priv pointer is not NULL before attempting to cleanup what it points to. When cs_dsp creates a control it calls wm_adsp_control_add_cb() so that wm_adsp can create its own private control data. There are two cases where private data is not created: 1. The control is a SYSTEM control, so an ALSA control is not created. 2. The codec driver has registered a control_add() callback that hides the control, so wm_adsp_control_add() is not called. When cs_dsp_remove destroys its control list it calls wm_adsp_control_remove() for each control. But wm_adsp_control_remove() was attempting to cleanup the private data pointed to by cs_ctl->priv without checking the pointer for NULL.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A NULL pointer dereference vulnerability exists in the Linux kernel's ASoC wm_adsp driver. When cs_dsp_remove destroys its control list, it calls wm_adsp_control_remove() for each control, but this function attempts to clean up private data pointed to by cs_ctl->priv without first checking if the pointer is NULL. Private data is not created for SYSTEM controls or for controls hidden by a custom control_add() callback, leading to the NULL dereference.

MitigationApply the upstream kernel patch which adds a NULL check for the priv pointer before cleanup in wm_adsp_control_remove(). This is a low-risk fix that prevents the crash when removing firmware controls in specific scenarios.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.16, < 6.1.176>= 6.2, < 6.6.143>= 6.7, < 6.12.94>= 6.13, < 6.18.36>= 6.19, < 7.0.13= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against affected ranges
    Run 'uname -r' or 'cat /proc/version' to get the running kernel version, then compare against: >= 5.16, < 6.1.176; >= 6.2, < 6.6.143; >= 6.7, < 6.12.94; >= 6.13, < 6.18.36; >= 6.19, < 7.0.13; = 7.1
    Affected if The kernel version falls within any of the listed affected ranges and the wm_adsp driver is in use
  2. Verify wm_adsp driver presence
    Check if the wm_adsp driver is loaded by running 'lsmod | grep wm_adsp' or check /sys/bus/platform/devices/*/driver for wm_adsp entries, or search kernel config for CONFIG_SND_SOC_WM_ADSP
    Affected if The wm_adsp driver is compiled into or loaded by the kernel
  3. Identify wm_adsp hardware on the system
    Check /proc/asound/cards, /sys/bus/platform/devices/, or dmesg output for wm_adsp, wm5102, wm5110, wm8998, or other Wolfson DSP device references
    Affected if Any Wolfson/Cirrus Logic DSP audio device using the wm_adsp driver is present
  4. Determine if SYSTEM controls exist or custom control_add() is used
    Examine the device tree or firmware configuration files for the wm_adsp device. Look for any control definitions that are marked as SYSTEM type, or review any custom board-level code that implements a custom control_add() callback for the cs_dsp driver
    Affected if The wm_adsp configuration uses SYSTEM controls or implements a custom control_add() callback that hides controls

The system is affected only if it runs a vulnerable kernel version, uses the wm_adsp driver with Wolfson DSP hardware, AND has SYSTEM controls or custom control_add() callbacks that result in NULL priv pointers during driver removal.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.176 / 6.6.143 / 6.12.94 or later
Fixed in 6.1.1766.6.1436.12.94
Interim mitigation

Apply the upstream kernel patch which adds a NULL check for the priv pointer before cleanup in wm_adsp_control_remove(). This is a low-risk fix that prevents the crash when removing firmware controls in specific scenarios.

Recommended fix High confidence

Linux kernel 6.1.176, 6.6.143, 6.12.94, or 6.18.36 (or later stable releases)

  1. Identify the currently running Linux kernel version using 'uname -r'
  2. Compare the kernel version against the affected ranges: >= 5.16 and < 6.1.176; >= 6.2 and < 6.6.143; >= 6.7 and < 6.12.94; >= 6.13 and < 6.18.36
  3. If affected, upgrade the kernel to a fixed release: 6.1.176 or later for the 6.1 branch, 6.6.143 or later for the 6.6 branch, 6.12.94 or later for the 6.12 branch, or 6.18.36 or later for the 6.13+ branch
  4. Reboot the system to load the fixed kernel
  5. Verify the fix is applied by checking the kernel version and confirming the wm_adsp module loads without NULL dereference errors
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with proprietary kernel modules or specific hardware drivers; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53350 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data