cve.bz

CVE-2025-54351 es iperf3: Unprotected Alternate Channel

10.0 criticalEPSS 0.5%Fix available

Critical (10.0) in es iperf3. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
In iperf before 3.19.1, net.c has a buffer overflow when --skip-rx-copy is used (for MSG_TRUNC in recv).

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-08-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-420 Unprotected Alternate Channel
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-54351 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-54351?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-54351?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-54351 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ES iperf3before 3.19.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu25.10, 26.10iperf3no fix listedUBUNTU-CVE-2025-54351
SUSEEnterprise Storage 7.1, Linux Enterprise Module for Package Hub 15 SP6, Linux Enterprise Module for Package Hub 15 SP7iperf3.19.1-150000.3.15.1SUSE-SU-2025:02749-1
openSUSELeap 15.6iperf3.19.1-150000.3.15.1SUSE-SU-2025:02749-1
openSUSETumbleweediperf3.19.1-1.1openSUSE-SU-2025:15414-1
Alpinev3.22, v3.23, v3.24iperf33.19.1-r0ALPINE-CVE-2025-54351
Alpaquita23iperf33.22-r0BELL-CVE-2025-54351
Alpaquita25, streamiperf33.19.1-r0BELL-CVE-2025-54351

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability was introduced with option --skip-rx-copy which was added after version 3.17.1. We currently have an older version of code in Red Hat Enterprise Linux(RHEL). No Red Hat products or offerings are affected by this vulnerability.

This vulnerability marked as Important instead a Moderate flaw due to the nature of the bug and the execution context. The flaw lies in the mishandling of buffer boundaries when the MSG_TRUNC flag is used in conjunction with the --skip-rx-copy option, leading to a classical buffer overflow. Unlike typical logic or input validation bugs that may merely crash an application, buffer overflows directly corrupt memory, potentially allowing arbitrary code execution depending on memory layout and platform-specific mitigations. Since iperf3 is often used in automated performance testing setups, CI pipelines, or even embedded environments, attackers could exploit this vulnerability remotely by sending crafted UDP packets, leading to memory corruption without any authentication. The use of MSG_TRUNC and skipped copy operations already places the application in a performance-optimized but less safe path, and the lack of proper bounds checking under these conditions makes it a memory safety issue—a class of bugs known to be exploitable and impactful

Red Hat's mitigation

No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10iperf3Not affected
Red Hat Enterprise Linux 7iperf3Not affected
Red Hat Enterprise Linux 8iperf3Not affected
Red Hat Enterprise Linux 9iperf3Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-54351.

References

Check your stackJSON