CVE-2025-67269
Gpsd integer overflow
- Published2 Jan 2026
Description
An integer underflow vulnerability exists in the `nextstate()` function in `gpsd/packet.c` of gpsd versions prior to commit `ffa1d6f40bca0b035fc7f5e563160ebb67199da7`. When parsing a NAVCOM packet, the payload length is calculated using `lexer->length = (size_t)c - 4` without checking if the input byte `c` is less than 4. This results in an unsigned integer underflow, setting `lexer->length` to a very large value (near `SIZE_MAX`). The parser then enters a loop attempting to consume this massive number of bytes, causing 100% CPU utilization and a Denial of Service (DoS) condition.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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/security/cve/CVE-2025-67269
- https://bugzilla.redhat.com/show_bug.cgi?id=2426810
- https://github.com/Jaenact/gspd_cve/blob/main/CVE-2025-67269/README.md
- https://gitlab.com/gpsd/gpsd
- https://gitlab.com/gpsd/gpsd/-/commit/ffa1d6f40bca0b035fc7f5e563160ebb67199da7
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-67269.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-67269 being actively exploited?
CVE-2025-67269 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.56%.
How severe is CVE-2025-67269?
CVE-2025-67269 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.56% probability of exploitation.
Which products are affected by CVE-2025-67269?
Affected products include Gpsd.
How do I fix CVE-2025-67269?
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-67269 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.