CVE-2025-67268

Exp

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.

Published: 2026-01-02 Last update: 2026-01-12 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-67268 is rated High Exploit Risk (70.9/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.24%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-67268

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-67268

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-04 0.13% 0.24% +0.11%
2 2026-02-26 0.16% 0.13% -0.03%
3 2026-02-13 — 0.16% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-67268

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-67268

OS Trackers for CVE-2025-67268

vendor priority summary link
alpine — CVE-2025-67268: 1 source package rows (gpsd); 8 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 0, open 8. https://security.alpinelinux.org/vuln/CVE-2025-67268
debian not yet assigned CVE-2025-67268 not yet assigned priority: Debian including 1 source packages (gpsd), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-67268
redhat high — https://access.redhat.com/security/cve/CVE-2025-67268
ubuntu medium CVE-2025-67268 medium priority: Ubuntu including 1 source packages (gpsd), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): released 5, needs-triage 3. https://ubuntu.com/security/CVE-2025-67268

Affected software / configurations for CVE-2025-67268

Vendor Product Version Raw CPE
gpsd_project gpsd < 3.27.1 cpe:2.3:a:gpsd_project:gpsd:*:*:*:*:*:*:*:*

References for CVE-2025-67268

cvelogic Threat Intelligence