CVE-2025-67269

CVE-2025-67269 is a high-severity vulnerability in Gpsd Project Gpsd with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-191.

Key facts

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.

Frequently asked questions

What is 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.
How severe is CVE-2025-67269?
CVE-2025-67269 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2025-67269 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-67269?
CVE-2025-67269 affects Gpsd Project Gpsd. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-67269?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-67269 have an EU (EUVD) identifier?
Yes. CVE-2025-67269 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-0658.
When was CVE-2025-67269 published?
CVE-2025-67269 was published on 2026-01-02 and last updated on 2026-06-30.

References

Affected products (1)

More vulnerabilities in Gpsd Project Gpsd

All CVEs affecting Gpsd Project Gpsd →

Other CWE-191 (Integer Underflow) vulnerabilities

Browse all CWE-191 (Integer Underflow) vulnerabilities →