# CVE-2025-8090: Vulnerability in the QNX Neutrino Kernel impacts the QNX Software Development Platform and QNX OS for Safety

> A local attacker with code execution capabilities can crash the QNX Neutrino kernel via a null pointer dereference in MsgRegisterEvent.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-j5j7-j8wm-qv7r

## What is CVE-2025-8090?

CVE-2025-8090 is a medium-severity vulnerability in BlackBerry Ltd QNX OS for Medical, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Null pointer dereference in the MsgRegisterEvent() system call could allow an attacker with local access and code execution abilities to crash the QNX Neutrino kernel.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-8090?


## How do I fix CVE-2025-8090?

No fix has been published for CVE-2025-8090 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8090 being exploited?

There is no known exploitation of CVE-2025-8090 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8090 and fix it if it is affected.

What it is: CVE-2025-8090 is a medium-severity vulnerability in BlackBerry Ltd QNX OS for Medical, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8090 in the wild and no public exploit code.

Affected product: BlackBerry Ltd QNX OS for Medical. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8090/ (Markdown: https://insights.sbomify.com/CVE-2025-8090/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8090
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8090
- OSV: https://osv.dev/vulnerability/CVE-2025-8090

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8090/
Summaries are generated and may contain mistakes; the official description above is the record.