# CVE-2025-67268: Memory corruption in n/a

> Heap-based out-of-bounds write in gpsd allows attackers to cause denial of service or execute arbitrary code via malformed NMEA2000 packets.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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-67268, GHSA-mp8p-xhgf-rpjv, RHSA-2026:1621, UBUNTU-CVE-2025-67268

## What is CVE-2025-67268?

CVE-2025-67268 is a critical memory corruption 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

gpsd before commit dc966aa contains a heap-based out-of-bounds write vulnerability in the drivers/driver_nmea2000.c file. The hnd_129540 function, which handles NMEA2000 PGN 129540 (GNSS Satellites in View) packets, fails to validate the user-supplied satellite count against the size of the skyview array (184 elements). This allows an attacker to write beyond the bounds of the array by providing a satellite count up to 255, leading to memory corruption, Denial of Service (DoS), and potentially arbitrary code execution.

Weakness: CWE-1285 (Improper Validation of Specified Index, Position, or Offset in Input), CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpsd` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:3.25-17.el10_0.1 |
| `gpsd-clients` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:3.25-17.el10_0.1 |
| `gpsd-clients-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:3.25-17.el10_0.1 |
| `gpsd-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:3.25-17.el10_0.1 |
| `gpsd-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:3.25-17.el10_0.1 |
| `python3-gpsd` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:3.25-17.el10_0.1 |
| `python3-gpsd-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 1:3.25-17.el10_0.1 |

Products: Gpsd Project Gpsd.

## How do I fix CVE-2025-67268?

Apply the vendor's patch.

## Is CVE-2025-67268 being exploited?

There is no known exploitation of CVE-2025-67268 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-58459](https://insights.sbomify.com/CVE-2026-58459/): gpsd gpsprof Command Injection via gnuplot plot title subtype field (high 8.4)
- [CVE-2025-67269](https://insights.sbomify.com/CVE-2025-67269/): Integer overflow in n/a (high 7.5)
- [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-67268 and fix it if it is affected.

What it is: CVE-2025-67268 is a critical memory corruption 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-67268 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-67268/ (Markdown: https://insights.sbomify.com/CVE-2025-67268/index.md)
```

## Sources

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

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