CVE-2025-8090VulnerabilityPublished 13 Jan 2026

CVE-2025-8090: BlackBerry QNX Software Development Platform · NULL Pointer Dereference

Affects BlackBerry QNX Software Development PlatformSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
BlackBerry LtdQNX Software Development Platform	Affected =7.1 and 7.0 =cpe:2.3:a:blackberry:qnx_software_development_platform:7.1:::::::* =cpe:2.3:a:blackberry:qnx_software_development_platform:7.0:::::::*	Fixed in–
BlackBerry LtdQNX OS for Safety	Affected =2.2.7 and earlier =cpe:2.3:o:blackberry:qnx_os_for_safety:2.2:7:::::: =2.1.4 and earlier =cpe:2.3:o:blackberry:qnx_os_for_safety:2.1:4:::::: =2.0.2 and earlier =cpe:2.3:o:blackberry:qnx_os_for_safety:2.0:2::::::	Fixed in–
BlackBerry Ltd.QNX OS for Medical	Affected =2.0.1 and earlier =cpe:2.3:o:blackberry:qnx_os_for_medical:2.0:1::::::	Fixed in–

AI-suggested

1. Restrict local access to systems running QNX to trusted personnel only, employing strict access controls and monitoring. 2. Implement robust endpoint security measures to prevent unauthorized code execution on QNX devices, including application whitelisting and behavioral monitoring. 3. Monitor system logs and kernel crash reports for signs of abnormal MsgRegisterEvent() failures or unexpected reboots indicative of exploitation attempts. 4. Isolate QNX-based embedded systems from general-purpose networks to reduce attack surface and lateral movement opportunities. 5. Engage with BlackBerry for timely updates and patches; apply security patches promptly once available. 6. Conduct regular security audits and penetration tests focusing on local access vectors to identify potential exploitation paths. 7. Develop incident response plans specific to embedded system denial of service scenarios to minimize downtime impact. 8. Consider deploying redundancy and failover mechanisms in critical QNX-dependent systems to maintain availability during incidents.

Description

CVE-2025-8090 is a medium severity vulnerability in BlackBerry's QNX Software Development Platform versions 7.0 and 7.1. It involves a NULL pointer dereference in the MsgRegisterEvent() system call, which can be triggered by an attacker with local access and code execution privileges to crash the QNX Neutrino kernel. This results in a denial of service condition without impacting confidentiality or integrity. Exploitation requires local access but no user interaction or elevated privileges beyond code execution. There are currently no known exploits in the wild and no patches publicly available. The vulnerability primarily affects embedded systems running QNX, commonly used in automotive, industrial, and critical infrastructure sectors. European organizations relying on QNX-based systems could face operational disruptions if exploited. Mitigation involves restricting local access, monitoring for abnormal kernel crashes, and applying vendor patches once released.

Impact

The primary impact of CVE-2025-8090 is denial of service through kernel crashes on systems running vulnerable QNX versions. For European organizations, this can disrupt operations in sectors heavily reliant on QNX embedded systems, such as automotive manufacturing, industrial automation, and critical infrastructure management. Automotive manufacturers using QNX for infotainment or vehicle control systems could experience system reboots or failures, potentially affecting production lines or vehicle safety features. Industrial control systems in utilities or manufacturing plants may face operational interruptions, leading to financial losses and safety risks. Although the vulnerability does not compromise confidentiality or integrity, availability disruptions in critical systems can have cascading effects on business continuity and safety compliance. The requirement for local access and code execution limits remote exploitation but insider threats or compromised local devices could leverage this flaw. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.blackberry.com/pkb/s/article/141027 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 02:53 UTC

WeaknessesCWE-476

Technical details

References

Community reviews

Related threats