CVE-2025-67269 Integer overflow in n/a

High 7.5 Published Updated

An integer underflow in gpsd allows attackers to cause a denial of service via high CPU utilization when parsing malformed NAVCOM packets.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-67269?

CVE-2025-67269 is a high-severity vulnerability in n/a, published on 2 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-191

Which versions are affected by CVE-2025-67269?

It affects 1 product.

Products include Gpsd Project Gpsd.

How do I fix CVE-2025-67269?

Apply the vendor's patch.

Is CVE-2025-67269 being exploited?

There is no known exploitation of CVE-2025-67269 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2025-67269, GHSA-xcj3-m9c5-2prq, OESA-2026-3035, UBUNTU-CVE-2025-67269.

Is CVE-2025-67269 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free