CVE-2025-67269
Gpsd Project Gpsd vulnerability
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.
Affected products
Gpsd. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Gpsd Project Gpsd runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- gitlab.com/gpsd/gpsd/-/commit/ffa1d6f40bca0b035fc7f5e563160ebb67199da7 · Patch
- github.com/Jaenact/gspd_cve/blob/main/CVE-2025-67269/README.md · Exploit
- gitlab.com/gpsd/gpsd
- access.redhat.com/errata/RHSA-2026:0770
- access.redhat.com/errata/RHSA-2026:0771
- access.redhat.com/security/cve/CVE-2025-67269
- bugzilla.redhat.com/show_bug.cgi?id=2426810
- security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-67269.json
- nvd.nist.gov/vuln/detail/CVE-2025-67269
- cve.org/CVERecord?id=CVE-2025-67269
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.