# CVE-2025-48964: Integer overflow in iputils > A crafted ICMP Echo Reply packet causes an integer overflow in ping statistics, leading to a denial of service. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jul 2025 - **Updated:** 26 Aug 2025 - **Also known as:** ALPINE-CVE-2025-48964, ALSA-2025:17558, ALSA-2026:18162, AZL-110348, AZL-65886, AZL-65889, BELL-CVE-2025-48964, GHSA-25fr-jw29-74f9, OESA-2025-2156, OESA-2025-2157, OESA-2025-2158, OESA-2025-2159, OESA-2025-2295, RHSA-2025:17558, RHSA-2025:17559, RHSA-2025:17560, RHSA-2026:18162, RLSA-2025:17558, RLSA-2026:18162, SUSE-SU-2025:02430-1, SUSE-SU-2025:02431-1, SUSE-SU-2025:02432-1, SUSE-SU-2025:02797-1, SUSE-SU-2025:20502-1, UBUNTU-CVE-2025-48964 ## What is CVE-2025-48964? CVE-2025-48964 is a medium-severity vulnerability in iputils, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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). Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2025-48964? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `iputils` | AlmaLinux:10 | All versions | 20240905-5.el10 | | `iputils` | AlmaLinux:9 | All versions | 20210202-11.el9_6.3 | | `iputils-ninfod` | AlmaLinux:9 | All versions | 20210202-11.el9_6.3 | | `iputils` | Red Hat:enterprise_linux:10.2 | All versions | 0:20240905-5.el10 | | `iputils-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:20240905-5.el10 | | `iputils-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:20240905-5.el10 | | `iputils-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:20210202-11.el9_6.3 | | `iputils-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:20210202-11.el9_6.3 | | `iputils-ninfod` | Red Hat:enterprise_linux:9::appstream | All versions | 0:20210202-11.el9_6.3 | | `iputils-ninfod-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:20210202-11.el9_6.3 | | `iputils` | Red Hat:enterprise_linux:9::baseos | All versions | 0:20210202-11.el9_6.3 | | `iputils-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:20210202-11.el9_6.3 | | `iputils-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:20210202-11.el9_6.3 | | `iputils-ninfod-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:20210202-11.el9_6.3 | | `iputils-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:20210202-8.el9_2.4 | | `iputils-debugsource` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:20210202-8.el9_2.4 | | `iputils-ninfod` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:20210202-8.el9_2.4 | | `iputils-ninfod-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:20210202-8.el9_2.4 | | `iputils` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:20210202-8.el9_2.4 | | `iputils-debuginfo` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:20210202-8.el9_2.4 | | `iputils-debugsource` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:20210202-8.el9_2.4 | | `iputils-ninfod-debuginfo` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:20210202-8.el9_2.4 | | `iputils-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:20210202-9.el9_4.5 | | `iputils-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:20210202-9.el9_4.5 | | `iputils-ninfod` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:20210202-9.el9_4.5 | | `iputils-ninfod-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:20210202-9.el9_4.5 | | `iputils` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:20210202-9.el9_4.5 | | `iputils-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:20210202-9.el9_4.5 | | `iputils-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:20210202-9.el9_4.5 | | `iputils-ninfod-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:20210202-9.el9_4.5 | | `iputils` | Rocky Linux:10 | All versions | 0:20240905-5.el10 | | `iputils` | Rocky Linux:9 | All versions | 0:20210202-11.el9_6.3 | | `iputils` | SUSE:Linux Enterprise Micro 5.1 | All versions | s20161105-150000.8.14.1 | | `iputils` | SUSE:Linux Enterprise Micro 5.2 | All versions | s20161105-150000.8.14.1 | | `iputils` | SUSE:Linux Enterprise Micro 5.3 | All versions | 20211215-150400.3.22.1 | | `iputils` | SUSE:Linux Enterprise Micro 5.4 | All versions | 20211215-150400.3.22.1 | | `iputils` | SUSE:Linux Enterprise Micro 5.5 | All versions | 20221126-150500.3.14.1 | | `iputils` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 20221126-150500.3.14.1 | | `iputils` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 20221126-150500.3.14.1 | | `iputils` | SUSE:Linux Enterprise Module for Server Applications 15 SP6 | All versions | 20211215-150400.3.22.1 | ## How do I fix CVE-2025-48964? Upgrade to a fixed version. ## Is CVE-2025-48964 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48964 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-48964 and fix it if it is affected. What it is: CVE-2025-48964 is a medium-severity vulnerability in iputils, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48964 exists. Affected product: iputils. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-48964/ (Markdown: https://insights.sbomify.com/CVE-2025-48964/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48964 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48964 - OSV: https://osv.dev/vulnerability/CVE-2025-48964 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-48964/ Summaries are generated and may contain mistakes; the official description above is the record.