LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50298: slimbus: qcom-ngd: cleanup in probe error path

In the Linux kernel, the following vulnerability has been resolved: slimbus: qcom-ngd: cleanup in probe error path Add proper error path in probe() to cleanup resources previously acquired/allocated to fix warnings visible during probe deferral: notifier callback qcom_slim_ngd_ssr_notify already registered WARNING: CPU: 6 PID: 70 at kernel/notifier.c:28 notifier_chain_register+0x5c/0x90 Modules linked in: CPU: 6 PID: 70 Comm: kworker/u16:1 Not tainted 6.0.0-rc3-next-20220830 #380 Call trace: notifier_chain_register+0x5c/0x90 srcu_notifier_chain_register+0x44/0x90 qcom_register_ssr_notifier+0x38/0x4c qcom_slim_ngd_ctrl_probe+0xd8/0x400 platform_probe+0x6c/0xe0 really_probe+0xbc/0x2d4 __driver_probe_device+0x78/0xe0 driver_probe_device+0x3c/0x12c __device_attach_driver+0xb8/0x120 bus_for_each_drv+0x78/0xd0 __device_attach+0xa8/0x1c0 device_initial_probe+0x18/0x24 bus_probe_device+0xa0/0xac deferred_probe_work_func+0x88/0xc0 process_one_work+0x1d4/0x320 worker_thread+0x2cc/0x44c kthread+0x110/0x114 ret_from_fork+0x10/0x20

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50298 is a Linux kernel issue in the Qualcomm NGD Slimbus driver. The public record describes incorrect cleanup when device probing is deferred, leading to duplicate notifier registration warnings. The sources do not provide CVSS, confirmed exploitation, or direct business impact details.

Executive priority

Treat as a maintenance-priority kernel fix unless vendor guidance raises severity. There is no provided evidence of exploitation or CVSS scoring, but kernel resource-cleanup bugs should still be addressed through normal patch governance.

Technical view

The flaw is in qcom_slim_ngd_ctrl_probe error handling. Resources registered or allocated before a probe failure were not fully cleaned up, so later deferred probes could re-register qcom_slim_ngd_ssr_notify and trigger kernel notifier warnings. Stable kernel commits are referenced as the resolution.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the Qualcomm NGD Slimbus driver path. The source lists Linux as affected but provides incomplete version-range clarity and no CPEs.

Exploitation context

The source bundle marks KEV false and provides no cited evidence of active exploitation. The described failure mode is a kernel warning during probe deferral, not a documented remote attack path.

Researcher notes

Evidence is narrow: the record describes a probe error-path cleanup defect and links four stable commits. No CWE, CVSS, exploit status, CPEs, or detailed affected ranges are provided, so exposure assessment depends on kernel branch and vendor backport status.

Mitigation direction

  • Review the referenced Linux stable commits for the applicable maintained kernel branch.
  • Update affected Linux kernels through vendor or distribution-supported packages.
  • Prioritize systems using Qualcomm platforms where the qcom-ngd Slimbus driver is enabled.
  • Check vendor advisories before applying unsupported kernel patches.

Validation and detection

  • Inventory Linux kernel versions against the CVE record and distribution advisories.
  • Determine whether the Qualcomm NGD Slimbus driver is present and enabled.
  • Review kernel logs for duplicate qcom_slim_ngd_ssr_notify notifier registration warnings.
  • Confirm the relevant stable commit or vendor backport is present.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50298 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe1ae85e1830e167a63f94007e50e088b86aa0a16, e1ae85e1830e167a63f94007e50e088b86aa0a16, e1ae85e1830e167a63f94007e50e088b86aa0a16, e1ae85e1830e167a63f94007e50e088b86aa0a16unaffected
LinuxLinux5.11, 0, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.