BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-53332High confidence

slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 24 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-53332 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-53332
76 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-40966

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2175Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260708Security Bulletin 8 July 2026 [PDF, 1MB]]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 8 July 2026 [PDF, 1MB]], published on 8 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53326 https://www.cve.org/CVERecord?id=CVE-2026-53326 Référence CVE CVE-2026-53327 https://www.cve.org/CVERecord?id=CVE-2026-53327 Référence CVE CVE-2026-53328 https://www.cve.org/CVERecord?id=CVE-2026-53328 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53330 https://www.cve.org/CVERecord?id=CVE-2026-53330 Référence CVE CVE-2026-53331 https://www.cve.org/CVERecord?id=CVE-2026-53331 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53333 https://www.cve.org/CVERecord?id=CVE-2026-53333 Référence CVE CVE-2026-53334 https://www.cve.org/CVERecord?id=CVE-2026-53334 Référence CVE CVE-2026-53335 https://www.cve.org/CVERecord?id=CVE-2026-53335 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53338 https://www.cve.org/CVERecord?id=CVE-2026-53338 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53340 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53326 https://www.cve.org/CVERecord?id=CVE-2026-53326 Référence CVE CVE-2026-53327 https://www.cve.org/CVERecord?id=CVE-2026-53327 Référence CVE CVE-2026-53328 https://www.cve.org/CVERecord?id=CVE-2026-53328 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53330 https://www.cve.org/CVERecord?id=CVE-2026-53330 Référence CVE CVE-2026-53331 https://www.cve.org/CVERecord?id=CVE-2026-53331 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53333 https://www.cve.org/CVERecord?id=CVE-2026-53333 Référence CVE CVE-2026-53334 https://www.cve.org/CVERecord?id=CVE-2026-53334 Référence CVE CVE-2026-53335 https://www.cve.org/CVERecord?id=CVE-2026-53335 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53338 https://www.cve.org/CVERecord?id=CVE-2026-53338 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53340 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53284 Référence CVE CVE-2026-53309 https://www.cve.org/CVERecord?id=CVE-2026-53309 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53326 https://www.cve.org/CVERecord?id=CVE-2026-53326 Référence CVE CVE-2026-53327 https://www.cve.org/CVERecord?id=CVE-2026-53327 Référence CVE CVE-2026-53328 https://www.cve.org/CVERecord?id=CVE-2026-53328 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53330 https://www.cve.org/CVERecord?id=CVE-2026-53330 Référence CVE CVE-2026-53331 https://www.cve.org/CVERecord?id=CVE-2026-53331 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53333 https://www.cve.org/CVERecord?id=CVE-2026-53333 Référence CVE CVE-2026-53334 https://www.cve.org/CVERecord?id=CVE-2026-53334 Référence CVE CVE-2026-53335 https://www.cve.org/CVERecord?id=CVE-2026-53335 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53338 https://www.cve.org/CVERecord?id=CVE-2026-53338 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53340 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53326 https://www.cve.org/CVERecord?id=CVE-2026-53326 Référence CVE CVE-2026-53327 https://www.cve.org/CVERecord?id=CVE-2026-53327 Référence CVE CVE-2026-53328 https://www.cve.org/CVERecord?id=CVE-2026-53328 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53330 https://www.cve.org/CVERecord?id=CVE-2026-53330 Référence CVE CVE-2026-53331 https://www.cve.org/CVERecord?id=CVE-2026-53331 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53333 https://www.cve.org/CVERecord?id=CVE-2026-53333 Référence CVE CVE-2026-53334 https://www.cve.org/CVERecord?id=CVE-2026-53334 Référence CVE CVE-2026-53335 https://www.cve.org/CVERecord?id=CVE-2026-53335 Référence CVE CVE-2026-53336 https://www.cve.org/CVERecord?id=CVE-2026-53336 Référence CVE CVE-2026-53337 https://www.cve.org/CVERecord?id=CVE-2026-53337 Référence CVE CVE-2026-53338 https://www.cve.org/CVERecord?id=CVE-2026-53338 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53340 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53267 Référence CVE CVE-2026-53270 https://www.cve.org/CVERecord?id=CVE-2026-53270 Référence CVE CVE-2026-53275 https://www.cve.org/CVERecord?id=CVE-2026-53275 Référence CVE CVE-2026-53289 https://www.cve.org/CVERecord?id=CVE-2026-53289 Référence CVE CVE-2026-53291 https://www.cve.org/CVERecord?id=CVE-2026-53291 Référence CVE CVE-2026-53297 https://www.cve.org/CVERecord?id=CVE-2026-53297 Référence CVE CVE-2026-53321 https://www.cve.org/CVERecord?id=CVE-2026-53321 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53331 https://www.cve.org/CVERecord?id=CVE-2026-53331 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53345 https://www.cve.org/CVERecord?id=CVE-2026-53345 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=CVE-2026-53369 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=CVE-2026-53374 Référence CVE CVE-2026-53375 https://www.cve.org/CVERecord?id=CVE-2026-53375 Référence CVE CVE-2026-53376 https://www.cve.org/CVERecord?id=CVE-2026-53376 Référence CVE CVE-2026-53379 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53297 Référence CVE CVE-2026-53313 https://www.cve.org/CVERecord?id=CVE-2026-53313 Référence CVE CVE-2026-53317 https://www.cve.org/CVERecord?id=CVE-2026-53317 Référence CVE CVE-2026-53318 https://www.cve.org/CVERecord?id=CVE-2026-53318 Référence CVE CVE-2026-53321 https://www.cve.org/CVERecord?id=CVE-2026-53321 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53331 https://www.cve.org/CVERecord?id=CVE-2026-53331 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53339 https://www.cve.org/CVERecord?id=CVE-2026-53339 Référence CVE CVE-2026-53345 https://www.cve.org/CVERecord?id=CVE-2026-53345 Référence CVE CVE-2026-53347 https://www.cve.org/CVERecord?id=CVE-2026-53347 Référence CVE CVE-2026-53350 https://www.cve.org/CVERecord?id=CVE-2026-53350 Référence CVE CVE-2026-53355 https://www.cve.org/CVERecord?id=CVE-2026-53355 Référence CVE CVE-2026-53356 https://www.cve.org/CVERecord?id=CVE-2026-53356 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1031Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-31610 Référence CVE CVE-2026-43216 https://www.cve.org/CVERecord?id=CVE-2026-43216 Référence CVE CVE-2026-45944 https://www.cve.org/CVERecord?id=CVE-2026-45944 Référence CVE CVE-2026-46093 https://www.cve.org/CVERecord?id=CVE-2026-46093 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53027 https://www.cve.org/CVERecord?id=CVE-2026-53027 Référence CVE CVE-2026-53226 https://www.cve.org/CVERecord?id=CVE-2026-53226 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=CVE-2026-53392 Référence CVE CVE-2026-53393 https://www.cve.org/CVERecord?id=CVE-2026-53393 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-63797 https://www.cve.org/CVERecord?id=CVE-2026-63797 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0982Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-52942 Référence CVE CVE-2026-53138 https://www.cve.org/CVERecord?id=CVE-2026-53138 Référence CVE CVE-2026-53157 https://www.cve.org/CVERecord?id=CVE-2026-53157 Référence CVE CVE-2026-53158 https://www.cve.org/CVERecord?id=CVE-2026-53158 Référence CVE CVE-2026-53159 https://www.cve.org/CVERecord?id=CVE-2026-53159 Référence CVE CVE-2026-53167 https://www.cve.org/CVERecord?id=CVE-2026-53167 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53329 https://www.cve.org/CVERecord?id=CVE-2026-53329 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53381 https://www.cve.org/CVERecord?id=CVE-2026-53381 Référence CVE CVE-2026-53382 https://www.cve.org/CVERecord?id=CVE-2026-53382 Référence CVE CVE-2026-53385 https://www.cve.org/CVERecord?id=CVE-2026-53385 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=CVE-2026-53392 Référence CVE CVE-2026-53393 https://www.cve.org/CVERecord?id=CVE-2026-53393 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-024990LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。slimbus: qcom-ngd-ctrlにおいて、ngd作成後にコールバックを登録するremoteprocがNGDドライバーのプローブと並行して起動する場合、またはPDRのルックアップが登録される時点でremoteprocが既に起動している場合、あるいは理論上ハードウェアから割り込みを受け取る場合に、これらのコールバックは初期化されていないデータを操作してしまいます。その結果、影響を受けるボードの起動に問題が発生します。例えば、以下の障害ログではqcom_slim_ngd_ssr_pdr_notify()が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...割り込みの有効化およびSSRとPDRの登録処理をNGDデバイス登録後まで移動しました。さらに、初期化をコントロールドライバーのプローブに移すことや、プラットフォームドライバーモデルを適用しない方法を採用することで、さらに改善が可能です。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.19, 5.10.260 ≤ 5.10.*, 5.15.212 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.94 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 Jul 2026 · Last source change 24 Jul 2026, 14:33 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-40966
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-40966↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-53332 · cve.blacktree.nl