Vulnerability 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 Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Gpsd Project | Gpsd | < 3.27.1 |
Related Weaknesses (CWE)
References
- https://github.com/Jaenact/gspd_cve/blob/main/CVE-2025-67269/README.mdExploitThird Party Advisory
- https://gitlab.com/gpsd/gpsdProduct
- https://gitlab.com/gpsd/gpsd/-/commit/ffa1d6f40bca0b035fc7f5e563160ebb67199da7Patch
FAQ
What is CVE-2025-67269?
CVE-2025-67269 is a vulnerability with a CVSS score of 7.5 (HIGH). 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, th...
How severe is CVE-2025-67269?
CVE-2025-67269 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-67269?
Check the references section above for vendor advisories and patch information. Affected products include: Gpsd Project Gpsd.