CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5) in gpsd project gpsd. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| gpsd_project:gpsd | before 3.27.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 11 | gpsd | 3.22-4+deb11u1 | DLA-4441-1 |
| Debian | 12 | gpsd | 3.22-4.1+deb12u1 | DEBIAN-CVE-2025-67269 |
| Debian | 13 | gpsd | 3.25-5+deb13u1 | DEBIAN-CVE-2025-67269 |
| Debian | 14 | gpsd | 3.27.5-0.1 | DEBIAN-CVE-2025-67269 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS | gpsd | no fix listed | UBUNTU-CVE-2025-67269 |
| Ubuntu | 22.04:LTS | gpsd | 3.22-4ubuntu2.1 | UBUNTU-CVE-2025-67269 |
| Ubuntu | 24.04:LTS | gpsd | 3.25-3ubuntu3.2 | UBUNTU-CVE-2025-67269 |
| Ubuntu | 25.10 | gpsd | 3.25-5ubuntu1.25.10.1 | UBUNTU-CVE-2025-67269 |
| Ubuntu | 26.04:LTS | gpsd | 3.27-1.1ubuntu1 | UBUNTU-CVE-2025-67269 |
| Red Hat | enterprise_linux:9::appstream | gpsd-minimal, gpsd-minimal-clients, gpsd-minimal-debuginfo and 2 more | 1:3.26.1-1.el9_7.1 | RHSA-2026:0771 |
| Red Hat | enterprise_linux:10.1 | gpsd, gpsd-clients, python3-gpsd and 4 more | 1:3.26.1-1.el10_1.1 | RHSA-2026:0770 |
| openSUSE | Tumbleweed | gpsd | 3.27.3-1.1 | openSUSE-SU-2026:10008-1 |
| AlmaLinux | 9 | gpsd-minimal, gpsd-minimal-clients | 1:3.26.1-1.el9_7.1 | ALSA-2026:0771 |
| AlmaLinux | 10 | gpsd, gpsd-clients, python3-gpsd | 1:3.26.1-1.el10_1.1 | ALSA-2026:0770 |
| Rocky Linux | 9 | gpsd-minimal | 1:3.26.1-1.el9_7.1 | RLSA-2026:0771 |
| Rocky Linux | 10 | gpsd | 1:3.26.1-1.el10_1.1 | RLSA-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 rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | gpsd-1:3.26.1-1.el10_1.1 | Fixed 2026-01-19 | RHSA-2026:0770 |
| Red Hat Enterprise Linux 9 | gpsd-minimal-1:3.26.1-1.el9_7.1 | Fixed 2026-01-19 | RHSA-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.