CVE Tools

CVE-2025-67269

CVE-2025-67269 affects Gpsd Project Gpsd (CVSS 7.5, High).

Public exploit available. Not confirmed exploited in the wild yet. Fixed in 3.27.1.

Check it yourself

OpenVAS · 17 checks

e.g. OID 1.3.6.1.4.1.25623.1.1.10.2026.0028

Run the check

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Gpsd Project GpsdAffected: < 3.27.1Upgrade to: 3.27.1Stated by: NVD
  • Open-source community Debian GNU/LinuxAffected: 11Upgrade to: not statedStated by: BDU
  • RusBITech-Astra Astra Linux Special EditionAffected: 1.7Upgrade to: not statedStated by: BDU
  • Canonical Ltd. UbuntuAffected: 22.04 LTSUpgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat Enterprise LinuxAffected: 9Upgrade to: not statedStated by: BDU

Versions as the sources state them. 3 more products have version data. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS48th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

A public exploit existed 115 days before the patch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Patch availablerecord updated
  4. OpenVAS check added
  5. Public exploit / PoCsource: github-poc
  6. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Questions about CVE-2025-67269

Is CVE-2025-67269 being exploited?
Not confirmed. Public exploit code exists (1 source), but CVE-2025-67269 is not in CISA KEV. EPSS puts the chance of exploitation in the next 30 days at 0.6%.
Which versions are affected by CVE-2025-67269?
Gpsd: < 3.27.1. Debian GNU/Linux: 11. Astra Linux Special Edition: 1.7. 5 more products are listed in the record.
How do I fix or mitigate CVE-2025-67269?
Upgrade to 3.27.1 or later. The advisory is on gitlab.com.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Gpsd, not every advisory. This one: public exploit.