CVE-2025-67268
Gpsd buffer overflow
- Published2 Jan 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:0770
- https://access.redhat.com/errata/RHSA-2026:0771
- https://access.redhat.com/errata/RHSA-2026:1621
- https://access.redhat.com/security/cve/CVE-2025-67268
- https://bugzilla.redhat.com/show_bug.cgi?id=2426835
- https://github.com/Jaenact/gspd_cve/blob/main/CVE-2025-67268/README.md
- https://github.com/ntpsec/gpsd/blob/master/drivers/driver_nmea2000.c
- https://github.com/ntpsec/gpsd/commit/dc966aa74c075d0a6535811d98628625cbfbe3f4
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-67268.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-67268 being actively exploited?
CVE-2025-67268 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.79%.
How severe is CVE-2025-67268?
CVE-2025-67268 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.79% probability of exploitation.
Which products are affected by CVE-2025-67268?
Affected products include Gpsd.
How do I fix CVE-2025-67268?
Upgrade affected software to a fixed version, for example Gpsd 3.27.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-67268 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.