dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53348

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 7.0.13 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: SDCA: fix NULL pointer dereference in sdca_dev_unregister_functions sdca_dev_unregister_functions() iterates over all SDCA function descriptors and calls sdca_dev_unregister() on each func_dev without checking for NULL. When a function registration has failed partway through, or the device cleanup races with probe deferral, func_dev entries may be NULL, leading to a kernel oops: BUG: kernel NULL pointer dereference, address: 0000000000000040 RIP: 0010:device_del+0x1e/0x3e0 Call Trace: sdca_dev_unregister_functions+0x37/0x60 [snd_soc_sdca] release_nodes+0x35/0xb0 devres_release_all+0x90/0x100 device_unbind_cleanup+0xe/0x80 device_release_driver_internal+0x1c1/0x200 bus_remove_device+0xc6/0x130 device_del+0x161/0x3e0 device_unregister+0x17/0x60 sdw_delete_slave+0xb6/0xd0 [soundwire_bus] sdw_bus_master_delete+0x1e/0x50 [soundwire_bus] ... sof_probe_work+0x19/0x30 [snd_sof] This was observed on a Lenovo ThinkPad X1 Carbon G14 (Panther Lake) with the SOF audio driver probe failing due to missing Panther Lake firmware, causing the subsequent cleanup of SoundWire devices to trigger the crash. Fix this with three changes: 1) Add a NULL guard in sdca_dev_unregister() so that callers do not need to pre-validate the pointer (defense in depth). 2) In sdca_dev_unregister_functions(), skip NULL func_dev entries and clear func_dev to NULL after unregistration, making the function idempotent and safe against double-invocation. 3) In sdca_dev_register_functions(), roll back all previously registered functions when a later one fails, so the function array is never left in a partially-populated state.

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 SDCA (Sound Device Control Architecture) driver. The function sdca_dev_unregister_functions() iterates over SDCA function descriptors and calls sdca_dev_unregister() on each func_dev without checking for NULL. When function registration fails partway through, or during device cleanup with probe deferral, func_dev entries may be NULL, causing a kernel oops in device_del(). The bug manifests during cleanup of SoundWire devices when audio driver probe fails (e.g., missing firmware).

MitigationThis is a kernel bug fix that requires patching the Linux kernel with the provided changes: adding NULL guards in sdca_dev_unregister(), skipping NULL entries and clearing func_dev after unregistration in sdca_dev_unregister_functions(), and implementing rollback logic in sdca_dev_register_functions() to prevent partial registration states. End users should apply kernel updates once the patch is upstreamed.

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:>= 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
    Run 'uname -r' or 'cat /proc/version' to obtain the running kernel version
    Affected if The kernel version is >= 6.19 and < 7.0.13, or equals 7.1
  2. Verify SDCA driver is present
    Check if the SDCA driver module exists in the kernel build: look for 'CONFIG_SND_SOC_SDCA' in /boot/config-* or /proc/config.gz, or check /sys/module for sdca-related modules
    Affected if CONFIG_SND_SOC_SDCA is set to 'y' (built-in) or 'm' (module) in the kernel configuration
  3. Identify SoundWire audio devices
    Run 'ls /sys/bus/soundwire/devices/' or check 'lspci | grep -i soundwire' to list SoundWire devices present in the system
    Affected if SoundWire devices are enumerated in the system, indicating the vulnerable code path could be exercised during device registration or cleanup
  4. Check for probe failure logs
    Review kernel logs with 'dmesg' or 'journalctl -k' for errors related to SDCA, SoundWire, or audio driver probe failures occurring during boot or device initialization
    Affected if Kernel logs show SDCA function registration failures, probe deferrals, or cleanup operations on SoundWire audio devices

A system is affected if it runs a vulnerable kernel version (>= 6.19, < 7.0.13 or = 7.1) AND uses SoundWire audio devices with the SDCA driver enabled, particularly if probe failures or device cleanup operations occur.

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 7.0.13 or later
Fixed in 7.0.13
Interim mitigation

This is a kernel bug fix that requires patching the Linux kernel with the provided changes: adding NULL guards in sdca_dev_unregister(), skipping NULL entries and clearing func_dev after unregistration in sdca_dev_unregister_functions(), and implementing rollback logic in sdca_dev_register_functions() to prevent partial registration states. End users should apply kernel updates once the patch is upstreamed.

Recommended fix High confidence

Linux Kernel 7.0.13+ or 7.2+ (7.1.x stable series after 7.1)

  1. 1. Identify the current running kernel version using `uname -r` or `cat /proc/version`
  2. 2. Check if the current version is affected: versions 6.19 through 7.0.12, or exactly version 7.1
  3. 3. If affected, upgrade the Linux kernel to version 7.0.13 or later in the 7.0.x stable series, or version 7.2 or later in the 7.1.x stable series
  4. 4. For distribution-specific systems, use the distro's package manager to update (e.g., `apt update && apt upgrade` for Debian/Ubuntu, `dnf update` for Fedora/RHEL)
  5. 5. After kernel update, reboot the system to load the fixed kernel
  6. 6. Verify the fix is applied by checking the kernel version after reboot with `uname -r`
Caveat Kernel upgrades may require rebooting production systems; ensure compatibility with existing drivers and software stack before upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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