Skip to main content
VulnerabilityPublished Updated

CVE-2025-67269: gpsd · Integer Underflow

Affects gpsdSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 3.26.1 soon.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.26.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade gpsd/gpsd to 3.26.1.

Affected software

ProductAffectedFixed in
GitHubgpsd/gpsdpkg:github/gpsd/gpsdOther threatsAffected
  • <3.26.1
Fixed in
  • 3.26.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update fixing this vulnerability is available in gpsd version 3.26.1. Users should apply the update provided by their vendor, such as the Red Hat Enterprise Linux 10 update packages. Refer to Red Hat advisory RHSA-2026:0770 for detailed update instructions. No additional mitigation is required once the update is applied.

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.

References

Community reviews

Loading reviews…