cve.bz

CVE-2025-67269 gpsd project gpsd: Integer Underflow (Wrap or Wraparound)

7.5 highExploit referenceEPSS 0.6%Fix available

High (7.5) in gpsd project gpsd. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-01-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-191 Integer Underflow (Wrap or Wraparound)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-67269 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-67269?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-67269?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-67269 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
gpsd_project:gpsdbefore 3.27.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11gpsd3.22-4+deb11u1DLA-4441-1
Debian12gpsd3.22-4.1+deb12u1DEBIAN-CVE-2025-67269
Debian13gpsd3.25-5+deb13u1DEBIAN-CVE-2025-67269
Debian14gpsd3.27.5-0.1DEBIAN-CVE-2025-67269
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTSgpsdno fix listedUBUNTU-CVE-2025-67269
Ubuntu22.04:LTSgpsd3.22-4ubuntu2.1UBUNTU-CVE-2025-67269
Ubuntu24.04:LTSgpsd3.25-3ubuntu3.2UBUNTU-CVE-2025-67269
Ubuntu25.10gpsd3.25-5ubuntu1.25.10.1UBUNTU-CVE-2025-67269
Ubuntu26.04:LTSgpsd3.27-1.1ubuntu1UBUNTU-CVE-2025-67269
Red Hatenterprise_linux:9::appstreamgpsd-minimal, gpsd-minimal-clients, gpsd-minimal-debuginfo and 2 more1:3.26.1-1.el9_7.1RHSA-2026:0771
Red Hatenterprise_linux:10.1gpsd, gpsd-clients, python3-gpsd and 4 more1:3.26.1-1.el10_1.1RHSA-2026:0770
openSUSETumbleweedgpsd3.27.3-1.1openSUSE-SU-2026:10008-1
AlmaLinux9gpsd-minimal, gpsd-minimal-clients1:3.26.1-1.el9_7.1ALSA-2026:0771
AlmaLinux10gpsd, gpsd-clients, python3-gpsd1:3.26.1-1.el10_1.1ALSA-2026:0770
Rocky Linux9gpsd-minimal1:3.26.1-1.el9_7.1RLSA-2026:0771
Rocky Linux10gpsd1:3.26.1-1.el10_1.1RLSA-2026:0770

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated Important for Red Hat because gpsd is susceptible to a remote denial-of-service condition triggered through malformed NAVCOM packets processed from untrusted input sources. A specially crafted packet can induce an unsigned integer underflow during packet length calculation in the NAVCOM parsing state machine, resulting in an excessively large length value and causing the parser to enter a non-terminating read state. Although the flaw does not directly lead to memory corruption, its severity is elevated because it affects a core parsing path that continuously processes streaming input and can be exploited with a single malformed packet, without authentication or sustained attacker interaction. The resulting sustained 100% CPU utilization renders the gpsd service unresponsive to all dependent clients, impacting system functionality wherever gpsd is exposed to network-based inputs or externally influenced serial devices.

Red Hat's mitigation

No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.

Exposure can be reduced by restricting gpsd from listening on network sockets, limiting input sources to trusted serial devices only, and ensuring the service is not accessible from untrusted networks. Deployments that do not require NAVCOM packet support should consider disabling or filtering such input where possible to further minimize risk.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10gpsd-1:3.26.1-1.el10_1.1Fixed 2026-01-19RHSA-2026:0770
Red Hat Enterprise Linux 9gpsd-minimal-1:3.26.1-1.el9_7.1Fixed 2026-01-19RHSA-2026:0771

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-67269.

References

Check your stackJSON