CVE-2025-48964

ping in iputils before 20250602 allows a denial of service (application error in adaptive ping mode or incorrect data collection) via a crafted ICMP Echo Reply packet, because a zero timestamp can lead to large intermediate values that have an integer overflow when squared during statistics calculations. NOTE: this issue exists because of an incomplete fix for CVE-2025-47268 (that fix was only about timestamp calculations, and it did not account for a specific scenario where the original timestamp in the ICMP payload is zero).

Published: 2025-07-22 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-48964 is rated Moderate Risk (49.4/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.51%). Review affected assets and schedule remediation.

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

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

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-22 0.39% 0.51% +0.12%
2 2026-05-20 0.51% 0.39% -0.12%
3 2026-05-18 — 0.51% —

Full EPSS history (7 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L 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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 2.5 [email protected]

Weakness enumeration for CVE-2025-48964

OS Trackers for CVE-2025-48964

vendor priority summary link
alpine — CVE-2025-48964: 1 source package rows (iputils); 6 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 1, open 5. https://security.alpinelinux.org/vuln/CVE-2025-48964
debian unimportant CVE-2025-48964 unimportant priority: Debian including 1 source packages (iputils), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-48964
redhat medium — https://access.redhat.com/security/cve/CVE-2025-48964
suse medium CVE-2025-48964 severity moderate: SUSE including 258 source package names (13.2-9.16:iputils-20221126-slfo.1.1_2.1, 14.2-3.12.62:iputils-20221126-150500.3.14.1, …), 543 product×package rows across 311 product lines (Container suse/hpc/warewulf4-x86_64/sle-hpc-node, Container suse/manager/5.0/x86_64/server, … (311 product lines)): Fixed 322, Known Affected 221. https://www.suse.com/security/cve/CVE-2025-48964/
ubuntu low CVE-2025-48964 low priority: Ubuntu including 1 source packages (iputils), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 4, released 4, not-affected 1. https://ubuntu.com/security/CVE-2025-48964

Affected software / configurations for CVE-2025-48964

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-48964

cvelogic Threat Intelligence