CVE-2026-90141
Description
A flaw was found in the Linux kernel's IP Virtual Server (IPVS) FTP helper. A remote attacker could exploit an integer overflow vulnerability in the ip_vs_ftp_get_addrport() function by sending a specially crafted FTP PASV/EPSV response. This could cause the FTP helper to configure data connections with truncated port or address values, potentially leading to a denial of service or misrouting of network traffic.
Statement
A moderate-impact flaw was found in the Linux kernel's IP Virtual Server (IPVS) FTP connection-tracking helper. The ip_vs_ftp_get_addrport() function in net/netfilter/ipvs/ip_vs_ftp.c accumulates decimal digits from FTP PASV/EPSV responses into a 16-bit port value and 8-bit address octets without checking for overflow. A crafted FTP PASV/EPSV response with an over-long port or address octet wraps the accumulated value, so the helper configures the FTP data connection with a truncated port or address, potentially causing a denial of service or misrouting of network traffic for deployments using the IPVS FTP helper. The kernel and kernel-rt packages in Red Hat Enterprise Linux 7, 8, 9, and 10, the kernels shipped in Red Hat In-Vehicle OS 2, and the RHEL CoreOS kernels used by OpenShift Container Platform 4 and 5 are affected; the Red Hat Enterprise Linux 6 kernel is out of support (OOSS). The fix for the affected products is currently deferred, so it will be delivered in a future scheduled kernel update rather than an immediate erratum; until then the residual risk is limited to disruption or misrouting of FTP data connections handled by the IPVS FTP helper. Red Hat rates this flaw as Moderate severity (CVSS 5.5, local attack vector, availability impact), which is lower than the upstream CVE record's rating of 7.3 with a network attack vector.
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 | 5.5 | N/A | 7.3 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | Low |
| Integrity Impact | None | N/A | Low |
| Availability Impact | High | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided. If the calculated result involves time values, then the product might crash when it encounters a time that is less than the previously-calculated time.
Integrity
Technical Impact: Modify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability,Other
Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.
Access Control
Technical Impact: Bypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Access Control
Technical Impact: Bypass Protection Mechanism; DoS: Crash, Exit, or Restart
If integer values are used in time-based, security-critical decisions, such as calculating expiration times or determining whether an event occurs within a specific time or date range, to cause an incorrect security decision. The consequences could even include "self-DoS" if the overflow produces a time value that is not accounted for in protection mechanism logic [REF-1570].
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.