Description
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.
Published: 2026-07-01
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A race condition in the Qualcomm SLIMBus NGD controller driver of the Linux kernel allows callbacks to be registered and invoked before the NGD device is fully initialized. When an interrupt or remote‑processor start occurs concurrently with the driver probe, the driver may attempt to use a NULL pointer, leading to a kernel panic during boot or system instability. This flaw is a classic null reference error (CWE‑476) that can prevent the board from booting. The vulnerable code resides in the slimbus/qcom‑ngd‑ctrl module, which is loaded on Qualcomm platforms that use the SLIMBus interconnect. The kernel’s remoteproc subsystem may start in parallel with this driver, and the SSR and PDR registration logic is executed too early, exposing uninitialized data structures. Based on the description and the nature of the flaw, the likely attack surface is limited to the kernel’s boot or firmware initialization phase. An attacker would need to control the timing of remote‑processor startup or trigger hardware interrupts at a precise moment, a scenario typically restricted to privileged firmware or an attacker with physical access to the device. The EPSS score shows <1 % probability, and the vulnerability is not listed in CISA’s KEV catalog, indicating no publicly known exploits and a low exploitation likelihood.

Affected Systems

Linux kernel builds that include the slimbus/qcom‑ngd‑ctrl module for Qualcomm devices are affected. The CNA does not pin specific kernel releases; therefore any kernel version that has not incorporated the upstream patch and still loads this module during startup is vulnerable. Devices that omit this module, or that run a patched kernel, are not at risk.

Risk and Exploitability

The low EPSS score and absence from KEV suggest that exploitation is unlikely in the wild. However, if an attacker can influence the remote‑processor initialization order or force hardware interrupts while the driver is probed, they could trigger a kernel panic and achieve a denial‑of‑service. Successful exploitation would require privileged control and could impact the entire system, preventing normal boot and operation.

Generated by OpenCVE AI on July 22, 2026 at 14:29 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that contains the upstream fix that defers interrupt enablement and SSR/PDR registration until after the NGD device has been registered.
  • If an upgrade is not immediately possible, unload or disable the slimbus/qcom‑ngd‑ctrl module at boot so its callbacks are not registered prematurely.
  • When the module must remain active, modify the boot sequence (e.g., via initramfs or init scripts) so that the remote‑processor services start only after the SLIMBus NGD driver has been fully initialized, ensuring all callbacks execute on a valid device state.

Generated by OpenCVE AI on July 22, 2026 at 14:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 04 Jul 2026 12:15:00 +0000


Thu, 02 Jul 2026 16:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-489
CWE-665

Thu, 02 Jul 2026 00:15:00 +0000


Wed, 01 Jul 2026 15:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-489
CWE-665

Wed, 01 Jul 2026 13:45:00 +0000

Type Values Removed Values Added
Description 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.
Title slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-04T11:51:07.922Z

Reserved: 2026-06-09T07:44:35.398Z

Link: CVE-2026-53332

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity :

Publid Date: 2026-07-01T00:00:00Z

Links: CVE-2026-53332 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-22T14:30:17Z

Weaknesses