CVE-2025-67268
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 · uneditedgpsd before commit dc966aa contains a heap-based out-of-bounds write vulnerability in the drivers/driver_nmea2000.c file. The hnd_129540 function, which handles NMEA2000 PGN 129540 (GNSS Satellites in View) packets, fails to validate the user-supplied satellite count against the size of the skyview array (184 elements). This allows an attacker to write beyond the bounds of the array by providing a satellite count up to 255, leading to memory corruption, Denial of Service (DoS), and potentially arbitrary code execution.
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 confidencegpsd before commit dc966aa has a heap-based out-of-bounds write in drivers/driver_nmea2000.c. The hnd_129540 function processes NMEA2000 PGN 129540 (GNSS Satellites in View) packets but does not validate the attacker-controlled satellite count against the 184-element skyview array limit, allowing writes up to 255 satellites and causing heap corruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.27.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify gpsd versionRun 'gpsd -V' or 'gpsd --version' to obtain the installed gpsd version numberAffected if Version is below 3.27.1
-
Confirm NMEA2000 driver is in useReview gpsd configuration files or running parameters to verify the NMEA2000 driver (driver_nmea2000) is enabled and communicating with NMEA2000 devicesAffected if NMEA2000 driver is configured and actively processing NMEA2000 messages
-
Check for PGN 129540 trafficMonitor network traffic or examine gpsd logs for incoming PGN 129540 (GNSS Satellites in View) packets on the NMEA2000 interfaceAffected if PGN 129540 packets are being received and processed by gpsd's NMEA2000 driver
A system is affected if gpsd version is below 3.27.1 AND the NMEA2000 driver is actively processing PGN 129540 packets from external sources.
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.
dbcve · scoped3.27.1
Upgrade gpsd to commit dc966aa or later which adds bounds validation; if unable to upgrade, restrict network access to gpsd service and validate NMEA2000 input sources.
3.27.1
- Upgrade gpsd to version 3.27.1 or later from the official ntpsec/gpsd repository
- Verify the upgrade was successful by running `gpsd --version` and confirming the version number
- If gpsd is running as a service, restart it to load the patched binary (e.g., `systemctl restart gpsd` or `service gpsd restart`)
- Test that the NMEA2000 PGN 129540 handling now properly validates the satellite count against the skyview array boundary
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67268 — 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-67268 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