CVE-2026-101276
Description
A flaw was found in iperf3. A heap use-after-free vulnerability—a condition where memory is accessed after being released—occurs when the server watchdog timer prematurely frees stream resources without first terminating active worker threads. A remote, unauthenticated attacker could trigger this timing flaw during a test to corrupt memory, potentially leading to arbitrary code execution or crashing the server to cause a Denial of Service (DoS).
Statement
A heap use-after-free was found in iperf3's server-side watchdog handling. When a running test trips the per-test watchdog, server_timer_proc() frees the test's streams without first cancelling or joining associated worker threads, so a still-running worker can dereference a freed iperf_stream. A remote, unauthenticated attacker who can reach an affected iperf3 server and cause the watchdog to fire while a worker is active can trigger heap memory corruption, crashing the server and potentially achieving code execution in the iperf3 process. The issue affects iperf3 3.21 (fixed in 3.22). Red Hat rates this Important (CVSSv3.1 8.1, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H); Attack Complexity is High because exploitation depends on the watchdog firing while a worker thread still references the stream.
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.1 | N/A | N/A |
| Attack Vector | Network | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | None | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | High | N/A | N/A |
| Integrity Impact | High | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Red Hat CVSS v3 Score Explanation
AC:H because exploitation requires the per-test watchdog (server_timer_proc) to fire while a stream worker thread is still running and can dereference the freed iperf_stream (race / upstream AT:P). Unlike CVE-2026-101283, default iperf3 servers without RSA auth are in scope. C/I/A:H reflect heap use-after-free memory corruption with process crash and potential code execution in the iperf3 process.
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.