CVE-2025-8090
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNull pointer dereference in the MsgRegisterEvent() system call could allow an attacker with local access and code execution abilities to crash the QNX Neutrino kernel.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA null pointer dereference vulnerability exists in the MsgRegisterEvent() system call of the QNX Neutrino kernel. An attacker with local access and the ability to execute code can trigger the dereference of a null pointer, causing a kernel crash and resulting in a denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm QNX Neutrino is runningRun 'uname -a' or 'uname -s' to identify the operating system. Look for 'QNX' in the output.Affected if The system is not running QNX Neutrino - this CVE does not apply to other operating systems.
-
Identify the QNX Neutrino kernel versionRun 'uname -v' or check '/usr/bin/version' if available. Compare the version number against any affected version ranges provided by QNX.Affected if The installed version falls within an affected version range (if such ranges become known).
-
Verify MsgRegisterEvent() system call availabilityAttempt to call MsgRegisterEvent() via a small test program or check system call tables if accessible. On QNX, you can examine /proc/trace or use 'showpio' kernel debugger hints.Affected if The system call exists and is callable - the vulnerability is present in the kernel.
-
Assess local access control scopeReview user accounts and group memberships via 'id', 'getent passwd', and 'getent group'. Determine which local users have shell or code execution privileges.Affected if Untrusted or low-privilege local users can execute code - they could trigger the null pointer dereference.
-
Check for services invoking MsgRegisterEvent()Review running processes and services. Use 'pidin' or 'proctree' to list processes. Check configuration files in /etc or /boot for services that may call MsgRegisterEvent().Affected if Services or processes that use MsgRegisterEvent() are running - they could be vectors for exploitation.
A user is affected if their system runs QNX Neutrino with an affected kernel version AND has the MsgRegisterEvent() system call available to local users who can execute code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply any vendor-supplied patches for QNX Neutrino. Until a patch is available, restrict local access to trusted personnel only and minimize the attack surface by disabling unnecessary services that could invoke MsgRegisterEvent().
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8090 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data