# CVE-2025-67269: Integer overflow in n/a

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

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jan 2026
- **Updated:** 15 Jul 2026
- **Also known as:** DEBIAN-CVE-2025-67269, GHSA-xcj3-m9c5-2prq, OESA-2026-3035, UBUNTU-CVE-2025-67269

## 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 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2025-67269?

It affects 1 product.


Products: 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.

## Other vulnerabilities in n/a

- [CVE-2025-67268](https://insights.sbomify.com/CVE-2025-67268/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-58459](https://insights.sbomify.com/CVE-2026-58459/): gpsd gpsprof Command Injection via gnuplot plot title subtype field (high 8.4)
- [CVE-2023-43628](https://insights.sbomify.com/CVE-2023-43628/): Integer overflow in GPSd (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67269 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2025-67269 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-67269/ (Markdown: https://insights.sbomify.com/CVE-2025-67269/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67269
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67269
- OSV: https://osv.dev/vulnerability/CVE-2025-67269

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-67269/
Summaries are generated and may contain mistakes; the official description above is the record.