CVE-2025-67268: gpsd before commit dc966aa contains a heap-based out-of-bounds write vulnerability in the drivers/driver_nm...
gpsd 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.
Security readout for executives and security teams
Plain-English summary
This flaw is a memory corruption bug in gpsd’s NMEA2000 satellite-view packet handling. A malicious or malformed packet can exceed an internal array limit, potentially crashing gpsd and, according to the CVSS assessment, could affect confidentiality, integrity, and availability.
Executive priority
Treat as urgent where gpsd processes network-reachable or untrusted NMEA2000 data, especially in operational systems relying on GNSS. Prioritize inventory first because the bundle lacks exact affected package versions.
Technical view
In drivers/driver_nmea2000.c, hnd_129540 handles PGN 129540 without validating a supplied satellite count against the 184-element skyview array. Counts up to 255 can trigger a heap out-of-bounds write. The record identifies CWE-122 and CWE-1285 and scores it CVSS 9.8.
Likely exposure
Exposure is likely limited to systems running gpsd code before commit dc966aa that process NMEA2000 GNSS Satellites in View packets. The bundle does not identify exact affected packaged versions or CPEs.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. It states network, low-complexity, unauthenticated exploitation is possible by supplying crafted packet data, but detailed exploitability in real deployments is not proven here.
Researcher notes
Key uncertainty is product/version mapping: affected vendor, product, versions, and CPEs are listed as n/a. The root issue is a count-to-array-bounds validation failure in hnd_129540, fixed by upstream commit dc966aa per the bundle.
Mitigation direction
Update gpsd to a build containing commit dc966aa or later.
Apply relevant vendor advisories, including listed Red Hat RHSAs where applicable.
If packaged fixes are unclear, check the operating system vendor’s CVE guidance.
Restrict gpsd/NMEA2000 inputs to trusted devices and networks until remediated.
Monitor gpsd crashes or memory-corruption symptoms after GNSS/NMEA2000 traffic.
Validation and detection
Inventory hosts and appliances running gpsd.
Confirm whether the deployed gpsd build predates commit dc966aa.
Check whether gpsd processes NMEA2000 PGN 129540 traffic in the environment.
Verify vendor package status against Red Hat CVE, CSAF, or errata guidance.
Confirm fixed packages or source revisions are deployed after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Validation of Specified Index, Position, or Offset in Input
Improper Validation of Specified Index, Position, or Offset in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.