Skip to main content

QNX Neutrino CVE-2026-4018

| EUVDEUVD-2026-44321 MEDIUM
Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)
2026-07-14 blackberry GHSA-vm3p-4vxh-gffg
6.4
CVSS 3.1 · Vendor: blackberry
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local access to QNX Neutrino system
  2. Delivery
    Obtain or abuse PROCMGR_AID_TRACE capability
  3. Exploit
    Issue crafted trace commands to TraceEvent()
  4. Execution
    Win kernel TOCTOU race condition window
  5. Impact
    Achieve kernel memory disclosure, data corruption, or crash

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
Exploitation Conditions

Two specific prerequisites must be simultaneously satisfied. First, the attacker must have local access to the QNX Neutrino system - the AV:L CVSS vector explicitly rules out remote exploitation. Second, the attacker's process must hold the PROCMGR_AID_TRACE process manager ability, a QNX-specific kernel capability that must be explicitly granted by a system administrator or embedded into a privileged application's process manager access control list; it is not available to ordinary local users by default. Beyond these prerequisites, the attacker must successfully win a kernel-level race condition (AC:H), which requires precise timing of concurrent trace commands within the narrow check-use window in the kernel - this is non-trivial and not automatable per SSVC. Exploitation is scoped to the vulnerable system only (S:U), limiting impact to the local QNX Neutrino kernel with no direct path to subsequent-system compromise through this flaw alone. The primary limiting factors for defenders are the non-default nature of PROCMGR_AID_TRACE and the race-condition reliability barrier.

Impact

All available signals converge on a moderate but access-gated real-world risk. The CVSS 3.1 score of 6.4 (Medium) is driven down from the high impact sub-scores (C:H/I:H/A:H) by two significant exploit barriers: AC:H reflecting the difficulty of reliably winning a kernel-level race condition, and PR:H reflecting the mandatory requirement for the PROCMGR_AID_TRACE process manager ability - a non-default, explicitly granted QNX capability. The AV:L vector eliminates any remote attack surface. EPSS at 0.09% (1st percentile) strongly corroborates that opportunistic or widespread exploitation is not anticipated. SSVC independently confirms exploitation status as none and marks the flaw as not automatable, consistent with the race-condition complexity barrier. The SSVC technical impact of total is notable and aligns with C:H/I:H/A:H - if an attacker does win the race, kernel-level compromise is the result. The most realistic threat actor is a malicious insider or a compromised privileged process within a QNX-based embedded deployment, particularly in safety or medical contexts where kernel availability carries heightened consequence. No conflicting signals between data sources are present; CVSS, EPSS, and SSVC are internally consistent.

Exploit ScenarioDerived

A local attacker - such as a compromised privileged process or a malicious insider - holding the PROCMGR_AID_TRACE capability on a QNX Neutrino system issues crafted trace commands to the TraceEvent() system call in rapid succession, timing concurrent kernel operations to win the race between the kernel's check and use of the targeted resource. Depending on which resource is corrupted in the race window, the attacker can exfiltrate sensitive kernel memory, overwrite kernel data structures to alter system behavior, or force a kernel panic, crashing the RTOS and disrupting safety- or medical-critical operations. No public proof-of-concept exploit has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 22, 2026

Time-of-check time-of-use (TOCTOU) race condition in the TraceEvent() system call of BlackBerry QNX Neutrino RTOS permits local attackers holding the PROCMGR_AID_TRACE kernel capability to trigger information disclosure, data tampering, or a kernel crash across three distinct product lines including safety- and medical-certified variants. Affected deployments span QNX Software Development Platform 7.0-7.1, QNX OS for Safety through 2.2.8, and QNX OS for Medical through 2.0.2. No public exploit or active exploitation has been identified; EPSS places this in the 1st percentile for near-term in-the-wild exploitation probability, and SSVC confirms exploitation status as none, though SSVC technical impact is rated total reflecting the kernel-level blast radius when conditions are met.

RemediationAI

The primary remediation is to apply the vendor-released patch documented in the BlackBerry security advisory at https://support.blackberry.com/pkb/s/article/141213. Exact fixed version numbers for each product line are not present in available input data and must be confirmed directly from the advisory, so administrators should review it for the specific patched release corresponding to their QNX SDP, QNX OS for Safety, or QNX OS for Medical deployment. Where patching cannot be applied immediately - common in certified safety or medical device environments requiring re-validation - the most effective compensating control is to audit and restrict assignment of the PROCMGR_AID_TRACE process manager ability to only those processes that strictly require kernel tracing; removing this ability from all non-essential principals eliminates the exploitation prerequisite entirely. Note that this control will disable kernel-level tracing and diagnostic workflows that depend on PROCMGR_AID_TRACE, which may impact development or monitoring tooling. Operators of safety-critical and medical systems should also review whether kernel crashes induced by this flaw could trigger fail-safe or fail-dangerous conditions in their deployment context and apply change management procedures accordingly.

Affected VersionsENISA

QNX OS for Medical 2.0.2 and earlier
QNX Software Development Platform cpe:2.3:a:blackberry:qnx_software_development_platform:7.0:*:*:*:*:*:*:*
QNX OS for Medical cpe:2.3:o:blackberry:qnx_os_for_medical:2.0:2:*:*:*:*:*:*
QNX OS for Safety cpe:2.3:o:blackberry:qnx_os_for_safety:2.1:5:*:*:*:*:*:*
QNX OS for Safety 2.0.3 and earlier
QNX Software Development Platform 7.0
QNX OS for Safety cpe:2.3:o:blackberry:qnx_os_for_safety:2.2:8:*:*:*:*:*:*
QNX Software Development Platform cpe:2.3:a:blackberry:qnx_software_development_platform:7.1:*:*:*:*:*:*:*
QNX OS for Safety 2.2.8 and earlier
QNX OS for Safety cpe:2.3:o:blackberry:qnx_os_for_safety:2.0:3:*:*:*:*:*:*
QNX OS for Safety 2.1.5 and earlier
QNX Software Development Platform 7.1

Affected Packages

euvd qnx_software_development_platform no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

QNX Neutrino is a microkernel-based POSIX-compliant real-time operating system (RTOS) produced by BlackBerry and widely deployed in safety-critical, automotive, industrial, and medical embedded systems. The TraceEvent() system call provides privileged kernel instrumentation and tracing functionality. CWE-367 (Time-of-Check Time-of-Use) describes a race condition class where a resource's state is validated at one point in time but consumed at a later point, creating a window in which a concurrent operation can alter that resource before it is used. In this vulnerability, specific trace commands within TraceEvent() contain such a race window inside the QNX Neutrino kernel itself. CPE data confirms three affected product families: QNX Software Development Platform (cpe:2.3:a:blackberry:qnx_software_development_platform:7.0 and 7.1), QNX OS for Safety (cpe:2.3:o:blackberry:qnx_os_for_safety versions 2.0.3, 2.1.5, and 2.2.8), and QNX OS for Medical (cpe:2.3:o:blackberry:qnx_os_for_medical:2.0:2). The vulnerability operates at the kernel level, meaning successful exploitation directly affects the integrity and availability of the OS itself rather than a userspace application.

Know when Qnx Software Development Platform gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (blackberry) PRIMARY 6.4 MEDIUM
AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 6.4 MEDIUM

Local-only attack vector, PROCMGR_AID_TRACE capability mandates PR:H, kernel race condition mandates AC:H; full C/I/A impact applies at kernel level.

3.1 AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (blackberry).

CVSS VectorVendor: blackberry

Attack Vector
Local
Attack Complexity
High
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

TOCTOU Race Condition in specific trace commands of the TraceEvent() system call could allow an attacker with local access and with the PROCMGR_AID_TRACE ability, to cause information disclosure, data tampering or a crash of the QNX Neutrino kernel.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche RTOS deployed in specialized safety, medical, and automotive embedded systems
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2013-2687 HIGH POC
7.8 Jul 12

Stack-based buffer overflow in the bpe_decompress function in (1) BlackBerry QNX Neutrino RTOS through 6.5.0 SP1 and (2)

CVE-2013-2688 MEDIUM POC
5.4 Jul 12

Buffer overflow in phrelay in BlackBerry QNX Neutrino RTOS through 6.5.0 SP1 in the QNX Software Development Platform al

CVE-2025-2474 CRITICAL
9.8 Jun 10

A security vulnerability in the PCX image codec in QNX SDP (CVSS 9.8) that allows an unauthenticated attacker. Critical

CVE-2021-32024 CRITICAL
9.8 Dec 13

A remote code execution vulnerability in the BMP image codec of BlackBerry QNX SDP version(s) 6.4 to 7.1 could allow an

CVE-2021-22156 CRITICAL
9.8 Aug 17

An integer overflow vulnerability in the calloc() function of the C runtime library of affected versions of BlackBerry®

CVE-2020-6932 CRITICAL
9.8 Aug 12

An information disclosure and remote code execution vulnerability in the slinger web server of the BlackBerry QNX Softwa

CVE-2017-3891 CRITICAL
9.6 Nov 14

In BlackBerry QNX Software Development Platform (SDP) 6.6.0, an elevation of privilege vulnerability in the default conf

CVE-2024-35213 CRITICAL
9.0 Jun 11

An improper input validation vulnerability in the SGI Image Codec of QNX SDP version(s) 6.6, 7.0, and 7.1 could allow an

CVE-2019-8998 HIGH
7.8 Jul 12

An information disclosure vulnerability leading to a potential local escalation of privilege in the procfs service (the

CVE-2026-4017 HIGH
7.4 Jul 14

Local information disclosure, data tampering, and denial of service in the BlackBerry QNX Neutrino kernel stems from a s

CVE-2023-32701 HIGH
7.1 Nov 14

Improper Input Validation in the Networking Stack of QNX SDP version(s) 6.6, 7.0, and 7.1 could allow an attacker to pot

CVE-2026-40272 HIGH
7.0 Jul 29

Arbitrary code execution and denial of service in BlackBerry QNX Software Development Platform arises from the tracepars

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy