cve.bz

CVE-2026-102253 esnet iperf3: Infinite Loop

8.7 highEPSS 0.4%

High (8.7) in esnet iperf3. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
iperf3 versions prior to 3.22 contains a denial of service vulnerability that allows unauthenticated remote attackers to crash-loop the server's UDP receive worker into an unrecoverable infinite loop by sending a single crafted control-channel parameter message followed by one 16-byte UDP datagram. Attackers can permanently pin the affected per-stream receive thread at approximately 100% CPU usage, rendering the server unusable until forcibly killed with SIGKILL, as the process does not respond to normal control-channel closure.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-30. 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-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-102253 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102253?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102253?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-2026-102253 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
esnet iperf3from 3.14 before 3.22

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13iperf3no fix listedDEBIAN-CVE-2026-102253
Debian14iperf33.22-0.1DEBIAN-CVE-2026-102253
Ubuntu26.04:LTS, 26.10, Pro:16.04:LTS and 4 moreiperf3no fix listedUBUNTU-CVE-2026-102253
Red Hatenterprise_linux:10.2iperf3, iperf3-debuginfo, iperf3-debugsource0:3.17.1-6.el10_2.2RHSA-2026:88207
Red Hatenterprise_linux:10.3iperf3, iperf3-debuginfo, iperf3-debugsource0:3.21-2.el10_3.1RHSA-2026:98085
SUSEEnterprise Storage 7.1, Linux Enterprise Module for Package Hub 15 SP7iperf3.22-150000.3.18.1SUSE-SU-2026:4678-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0iperf3.21-160000.1.1SUSE-SU-2026:24234-1
SUSELinux Micro Extras 6.2iperf3.21-160000.1.1SUSE-SU-2026:24178-1
openSUSELeap 16.0iperf3.21-160000.1.1openSUSE-SU-2026:22090-1
openSUSETumbleweediperf3.22-1.1openSUSE-SU-2026:12060-1
AlmaLinux10iperf33.17.1-6.el10_2.2ALSA-2026:88207
AlmaLinux10iperf33.21-2.el10_3.1ALSA-2026:98085
Rocky Linux10iperf30:3.17.1-6.el10_2.2RLSA-2026:88207
Rocky Linux10iperf3, iperf3-debuginfo, iperf3-debugsource0:3.21-2.el10_3.1RLSA-2026:98085
Azure Linux3iperf33.17.1-7AZL-105051
Alpaquita23, 25, streamiperf33.22-r0BELL-CVE-2026-102253

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity for Red Hat because an unauthenticated remote attacker can trigger complete denial of service through severe CPU resource exhaustion without requiring elevated privileges. While iperf3 is predominantly invoked on demand for diagnostic network throughput benchmarking rather than deployed as a continuous background daemon, any active listener exposed to untrusted network traffic can be forced into an unresponsive state. The affected process ceases responding to control messages and requires manual administrative termination via SIGKILL, rendering benchmarking services unavailable.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10iperf3-0:3.17.1-6.el10_2.2Fixed 2026-10-22RHSA-2026:88207
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-2026-102253.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON