CVE-2025-67269
BaseFortify
Publication date: 2026-01-02
Last updated on: 2026-01-09
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gpsd_project | gpsd | to 3.27.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-191 | The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an integer underflow in the nextstate() function of gpsd's packet.c file. When parsing a NAVCOM packet, the code calculates the payload length by subtracting 4 from an input byte value without checking if that value is less than 4. If it is, this causes an unsigned integer underflow, setting the length to a very large number. The parser then tries to process this huge length, leading to excessive CPU usage and a denial-of-service condition. [2]
How can this vulnerability impact me? :
The vulnerability can cause the gpsd service to consume 100% CPU resources by entering a loop processing an extremely large payload length. This results in a denial-of-service (DoS) condition, potentially making the GPS service unavailable or unresponsive. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the gpsd process for unusually high CPU utilization, as the integer underflow causes the parser to enter a loop consuming 100% CPU. You can use commands like 'top' or 'htop' on Linux to observe CPU usage of the gpsd process. Additionally, inspecting logs for malformed NAVCOM packets or unusual gpsd behavior may help. Specific commands include: 'top -p $(pidof gpsd)' or 'htop' and filtering for gpsd, and 'tcpdump' or 'wireshark' to capture and analyze NAVCOM packets for anomalies. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update gpsd to a version that includes the fix from commit ffa1d6f40bca0b035fc7f5e563160ebb67199da7, which prevents the integer underflow in the nextstate() function. Until the update can be applied, consider restricting or filtering NAVCOM packets from untrusted sources to prevent malicious packets from triggering the vulnerability. [2]