Integer overflow in Gpsd Project

CVE-2025-67269

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

EPSS exploit prediction

EPSS: 0.006 (45.7th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 46th percentile — 45.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2025-67269: held from 0.005 to 0.006.

EPSS over last 30 days · oldest: 0.005 · newest: 0.006 · change: +0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2025-67269?
CVE-2025-67269 is a high-severity vulnerability in Gpsd Project, classified under Integer Underflow. CVSS score: 7.5/10. Published 2026-01-02.
How severe is CVE-2025-67269?
High severity. CVSS v3 base score is 7.5 out of 10.