dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53332

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 5.10.260 / 6.12.94 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available 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: slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd When the remoteproc starts in parallel with the NGD driver being probed, or the remoteproc is already up when the PDR lookup is being registered, or in the theoretical event that we get an interrupt from the hardware, these callbacks will operate on uninitialized data. This result in issues to boot the affected boards. One such example can be seen in the following fault, where qcom_slim_ngd_ssr_pdr_notify() schedules work on the NULL ngd_up_work. [ 21.858578] ------------[ cut here ]------------ [ 21.858745] WARNING: kernel/workqueue.c:2338 at __queue_work+0x5e0/0x790, CPU#2: kworker/2:2/116 ... [ 21.859251] Call trace: [ 21.859255] __queue_work+0x5e0/0x790 (P) [ 21.859265] queue_work_on+0x6c/0xf0 [ 21.859273] qcom_slim_ngd_ssr_pdr_notify+0x110/0x150 [slim_qcom_ngd_ctrl] [ 21.859304] qcom_slim_ngd_ssr_notify+0x24/0x40 [slim_qcom_ngd_ctrl] [ 21.859318] notifier_call_chain+0xa4/0x230 [ 21.859329] srcu_notifier_call_chain+0x64/0xb8 [ 21.859338] ssr_notify_start+0x40/0x78 [qcom_common] [ 21.859355] rproc_start+0x130/0x230 [ 21.859367] rproc_boot+0x3d4/0x518 ... Move the enablement of interrupts, and the registration of SSR and PDR until after the NGD device has been registered. This could be further refined by moving initialization to the control driver probe and by removing the platform driver model from the picture.

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

Race condition in Linux kernel slimbus qcom-ngd-ctrl driver where SSR (subsystem restart) and PDR (power domain recognition) callbacks are registered before the NGD device is fully initialized. When the remoteproc starts in parallel with driver probing or is already running, these callbacks fire on uninitialized data structures, causing NULL pointer dereferences (e.g., queue_work on NULL ngd_up_work).

MitigationApply the kernel patch that reorders initialization to register callbacks only after the NGD device is fully created and registered, preventing premature callback invocation.

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:>= 4.19, < 5.10.260>= 5.11, < 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 read `/proc/version` to obtain the running kernel version. Compare against the affected ranges: >= 4.19 and < 5.10.260; >= 5.11 and < 6.12.94; >= 6.13 and < 6.18.36; >= 6.19 and < 7.0.13; or exactly 7.1
    Affected if Kernel version matches any of the listed affected ranges and the system uses the vulnerable driver
  2. Verify qcom-ngd-ctrl slimbus driver is present
    Check if the kernel configuration includes `CONFIG_QCOM_SLIM_NGD_CTRL` by reading `/boot/config-$(uname -r)` or check if the module `qcom_slim_ngd` is loaded via `lsmod | grep slim`
    Affected if The driver is compiled into the kernel or loaded as a module on an affected kernel version
  3. Confirm Qualcomm Slimbus hardware is present
    Check for Slimbus controller hardware in the system by examining `lspci` output for Qualcomm devices, or check device tree entries in `/sys/firmware/devicetree` for `slimbus` or `qcom,slim-ngd-ctrl` nodes
    Affected if The system contains Qualcomm Slimbus hardware and runs an affected kernel version
  4. Check if remoteproc subsystem is active
    Examine if remoteproc is enabled and running by checking `lsmod | grep remoteproc` or viewing `/sys/class/remoteproc/` directory contents
    Affected if Remoteproc is active on a system with the vulnerable driver and affected kernel, creating the conditions for the race condition

A system is affected if it runs a kernel version within the affected ranges AND has the qcom-ngd-ctrl driver enabled with Qualcomm Slimbus hardware present, especially when remoteproc is active.

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 5.10.260 / 6.12.94 / 6.18.36 or later
Fixed in 5.10.2606.12.946.18.36
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch that reorders initialization to register callbacks only after the NGD device is fully created and registered, preventing premature callback invocation.

Recommended fix High confidence

5.10.260, 6.12.94, 6.18.36, or 7.0.13 (depending on which major version branch you are on)

  1. Upgrade the Linux kernel to a version >= 5.10.260 if currently running >= 4.19 and < 5.10.260
  2. OR upgrade to a version >= 6.12.94 if currently running >= 5.11 and < 6.12.94
  3. OR upgrade to a version >= 6.18.36 if currently running >= 6.13 and < 6.18.36
  4. OR upgrade to a version >= 7.0.13 if currently running >= 6.19 and < 7.0.13
Caveat Kernel upgrades may require rebuilding out-of-tree kernel modules; ensure driver compatibility with the target kernel version

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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