dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53052

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.1.175 / 6.6.141 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available 8 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: qcom: qdsp6: topology: check widget type before accessing data Check widget type before accessing the private data, as this could a virtual widget which is no associated with a dsp graph, container and module. Accessing witout check could lead to incorrect memory access.

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 · moderate confidence

In the Linux kernel's ASoC (Audio System on Chip) Qualcomm DSP6 topology driver, code accesses widget private data without first validating the widget type. Virtual widgets lack association with DSP graphs, containers, and modules, so unconditional access can lead to incorrect memory access and potential out-of-bounds read/write conditions.

MitigationApply the kernel patch which adds a widget type validation check before accessing private data structures; this is a code-level fix requiring kernel rebuild. Prior to patching, monitor kernel logs for any audio-related crashes or memory errors.

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.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

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 your running Linux kernel version
    Run `uname -r` to get the kernel version, then compare it against the affected ranges: 5.16 to 6.1.174, 6.2 to 6.6.140, 6.7 to 6.12.90, 6.13 to 6.18.32, or 6.19 to 7.0.9
    Affected if The kernel version falls within any of the affected ranges listed
  2. Verify the ASoC Qualcomm DSP6 driver is present
    Check for the presence of the q6dsp6 driver files in the kernel module directory, typically under /lib/modules/$(uname -r)/kernel/sound/soc/qcom/ or list loaded sound modules with `lsmod | grep q6dsp`
    Affected if The q6dsp6 or q6dsp6lsm modules are loaded or present on the system
  3. Check if a Qualcomm DSP6 sound card is enumerated
    Examine /proc/asound/cards or run `aplay -l` to list available sound cards, looking for entries associated with Qualcomm DSP devices
    Affected if A sound card using the Qualcomm DSP6 topology driver is present and active
  4. Identify if virtual widgets are used in the topology
    Inspect the DSP topology configuration files or examine the runtime widget list through the ALSA control interface if topology debugging is enabled, looking for widgets of type SND_SOC_DAPM_VIRTUAL
    Affected if Virtual widgets are defined in the active DSP topology configuration

You are affected if your kernel version is within the vulnerable ranges AND the Qualcomm DSP6 topology driver is loaded with a topology containing virtual widgets.

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.175 / 6.6.141 / 6.12.91 or later
Fixed in 6.1.1756.6.1416.12.91
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch which adds a widget type validation check before accessing private data structures; this is a code-level fix requiring kernel rebuild. Prior to patching, monitor kernel logs for any audio-related crashes or memory errors.

Recommended fix High confidence

Upgrade to kernel 6.1.175+ (for 6.1.y), 6.6.141+ (for 6.2-6.6.y), 6.12.91+ (for 6.7-6.12.y), or 6.18.33+ (for 6.13+)

  1. 1. Check the current running kernel version using 'uname -r' or 'cat /proc/version'
  2. 2. Identify which kernel branch (6.1.y, 6.6.y, 6.12.y, or 6.13+) your current version belongs to
  3. 3. For 6.1.y branch: upgrade to kernel version 6.1.175 or later
  4. 4. For 6.2-6.6.y branch: upgrade to kernel version 6.6.141 or later
  5. 5. For 6.7-6.12.y branch: upgrade to kernel version 6.12.91 or later
  6. 6. For 6.13-6.18.y branch: upgrade to kernel version 6.18.33 or later
  7. 7. After upgrading, verify the patch is applied by checking the relevant source file in sound/soc/qcom/qdsp6/q6lsm.c for the widget type check
Caveat Kernel upgrades may introduce compatibility changes with drivers, modules, or user-space software; test thoroughly in staging before production deployment

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53052 — 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-53052 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