Is CVE-2025-67269 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-67269 being exploited in the wild.

How severe is CVE-2025-67269?

High severity, with a CVSS score of 7.5, published 2 January 2026.

Which products and versions are affected?

Gpsd Project Gpsd versions prior to 3.27.1; Red Hat Enterprise Linux AppStream affected.

Is there a fix for CVE-2025-67269?

A patch was published on 2025-12-03: Commit ffa1d6f40bca0b035fc7f5e563160ebb67199da7 merged to fix the underflow. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-67269 attacked?

It is attacked over the network or from the adjacent network or with local access, in a software library.

Am I affected by CVE-2025-67269?

Check whether you run Gpsd Project Gpsd or Red Hat Enterprise Linux AppStream at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-67269: gpsd integer underflow in NAVCOM packet parsing

CVE-2025-67269 · Severity: high · CVSS 7.5 · Published 2026-01-02

A vulnerability in the gpsd service, which manages GPS and navigation sensors, can allow an attacker to crash the service or make it unresponsive. By sending a specially crafted navigation packet, an attacker can force the system to consume 100% of its processing power, leading to a denial of service. This could disrupt operations for any application relying on precise location or timing data from the affected system.

Technologies: Gpsd Project Gpsd, Red Hat Enterprise Linux AppStream. Vendors: Gpsd Project, Red Hat.

Quick answers

Is CVE-2025-67269 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-67269 being exploited in the wild.
How severe is CVE-2025-67269?: High severity, with a CVSS score of 7.5, published 2 January 2026.
Which products and versions are affected?: Gpsd Project Gpsd versions prior to 3.27.1; Red Hat Enterprise Linux AppStream affected.
Is there a fix for CVE-2025-67269?: A patch was published on 2025-12-03: Commit ffa1d6f40bca0b035fc7f5e563160ebb67199da7 merged to fix the underflow. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-67269 attacked?: It is attacked over the network or from the adjacent network or with local access, in a software library.
Am I affected by CVE-2025-67269?: Check whether you run Gpsd Project Gpsd or Red Hat Enterprise Linux AppStream at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An integer underflow exists in the nextstate() function within gpsd/packet.c when handling NAVCOM_ID states. The vulnerability occurs because the lexer calculates the payload length by subtracting 4 from an input byte without verifying if the byte is at least 4. If the byte is smaller, an unsigned integer underflow occurs, resulting in a length value near SIZE_MAX. The parser then enters a loop attempting to consume this massive amount of data, leading to 100% CPU utilization and a permanent hang of the daemon. This can be triggered via any input channel supported by gpsd, including network sockets (TCP port 2947) or local serial devices. The issue is fixed in version 3.27.1.

Affected products

gpsd project gpsd versions prior to 3.27.1
Red Hat Red Hat Enterprise Linux AppStream (v. 9) affected
Red Hat Red Hat Enterprise Linux AppStream (v. 10) affected

Timeline

2025-12-03: patched: Commit ffa1d6f40bca0b035fc7f5e563160ebb67199da7 merged to fix the underflow.
2026-01-02: disclosed: Public disclosure of CVE-2025-67269.
2026-01-19: advisory: Red Hat issued security advisory RHSA-2026:0770.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.