CVE-2025-67269: An integer underflow vulnerability exists in the `nextstate()` function in `gpsd/packet.c` of gpsd versions pr

Q: How do I fix CVE-2025-67269?

gpsd: upgrade to 3.27.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-67269 being exploited?

CVE-2025-67269 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-67269 affect?

CVE-2025-67269 affects gpsd. Severity is high (CVSS 7.5). 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 `le

Q: How urgent is CVE-2025-67269?

Priority 48/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2025-67269 is a high-severity flaw (CVSS 7.5) affecting gpsd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 the

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 53%)
CISA exploited list	No
Weakness	CWE-191
Published	2026-01-02
Last modified	2026-07-15

Publisher (CNA): MITRE · Vendor: gpsd project

Last updated 2026-07-15 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-01-02 16:17 UTCPublished CVE record published
2026-07-15 02:17 UTCUpdated Record last modified

gpsd project gpsd UPGRADE

Affected: < 3.27.1

Fixed in: 3.27.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gpsd || rpm -q gpsd || gpsd --version

2. UPGRADE to 3.27.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gpsd

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gpsd

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-67269?

gpsd: upgrade to 3.27.1. Exact commands for each OS are on this page.

Is CVE-2025-67269 being exploited?

CVE-2025-67269 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-67269 affect?

CVE-2025-67269 affects gpsd. Severity is high (CVSS 7.5). 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 `le

How urgent is CVE-2025-67269?

Priority 48/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-58459 HIGH 7.8 UPGRADE gpsd through release-3.27.5, fixed at commit 4c06658, contains a command injection vulnerability in gpsprof th
CVE-2025-67268 CRITICAL 9.8 UPGRADE gpsd before commit dc966aa contains a heap-based out-of-bounds write vulnerability in the drivers/driver_nmea2

References

← Back to latest CVEs