LiveActive security incident?Get immediate response
CVE Record

CVE-2025-67269: An integer underflow vulnerability exists in the `nextstate()` function in `gpsd/packet.c` of gpsd versions...

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-67269 can make gpsd consume all CPU while processing a malformed NAVCOM packet. The impact is service availability, not data theft or code execution. Systems depending on gpsd for GPS or time/location data could lose that service until the process is recovered or updated.

Executive priority

Treat as a high-priority availability fix for systems where gpsd supports operational GPS, navigation, telemetry, or time/location workflows. It is less urgent for isolated systems with trusted inputs, but the low-complexity network vector warrants prompt patch tracking.

Technical view

gpsd before commit ffa1d6f40bca0b035fc7f5e563160ebb67199da7 has an integer underflow in packet.c nextstate(). A NAVCOM payload length is computed as (size_t)c - 4 without checking c < 4, producing a near-SIZE_MAX length and a parser loop that drives 100% CPU. CVSS is 7.5, network exploitable, availability-only.

Likely exposure

Exposure is plausible where gpsd processes NAVCOM packets from untrusted or network-reachable sources. The bundle does not identify exact affected product versions or CPEs, so inventory should focus on gpsd builds older than the named fixing commit and downstream vendor packages.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. Public researcher material is referenced, and the vulnerability description is specific enough to support defensive validation, but exploitation status should not be assumed beyond denial-of-service risk.

Researcher notes

Key evidence is the described underflow in nextstate() and the fixing commit. The source bundle lacks exact affected version ranges, CPEs, and confirmed exploitation data. Avoid expanding scope beyond gpsd builds prior to the referenced commit and downstream packages covered by vendor advisories.

Mitigation direction

  • Update gpsd to a build containing commit ffa1d6f40bca0b035fc7f5e563160ebb67199da7.
  • Apply relevant downstream vendor advisories, including Red Hat RHSA-2026:0770 and RHSA-2026:0771 where applicable.
  • Limit gpsd exposure to trusted data sources and trusted network paths.
  • Monitor gpsd CPU saturation and service restarts until patched.
  • Check vendor guidance if your distribution package status is unclear.

Validation and detection

  • Inventory systems running gpsd and record package versions or source commit identifiers.
  • Confirm whether deployed builds predate commit ffa1d6f40bca0b035fc7f5e563160ebb67199da7.
  • Review vendor advisories for your operating system and package stream.
  • Check whether gpsd accepts NAVCOM input from untrusted devices or networks.
  • Verify monitoring can detect sustained gpsd CPU saturation.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-191: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-67269 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-67269Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPgpsd: gpsd: Denial of Service due to malformed NAVCOM packet parsing
other:Red Hat severity ratingcvssV3_1
  • 2026-01-02T16:01:42.941Z: Reported to Red Hat.
  • 2026-01-02T00:00:00.000Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-191

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-191 · source CWE mapping

Integer Underflow (Wrap or Wraparound)

Integer Underflow (Wrap or Wraparound) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs