# CVE-2026-90141: ipvs: fix integer overflow in ftp helper port/address parsing

> An integer overflow in the Linux kernel IPVS FTP helper allows attackers to truncate port or address values via crafted responses, potentially disrupting connection tracking.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102327, BELL-CVE-2026-90141, DEBIAN-CVE-2026-90141, GHSA-hcq4-7chf-c998, UBUNTU-CVE-2026-90141

## What is CVE-2026-90141?

CVE-2026-90141 is a high-severity vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ipvs: fix integer overflow in ftp helper port/address parsing

ip_vs_ftp_get_addrport() accumulates decimal digits into a __u16
(hport) and into unsigned char (p[]) without checking for overflow.
A crafted FTP PASV/EPSV response with an over-long port or address
octet wraps the value, so the helper configures the data connection
with a truncated port/address.

The netfilter conntrack FTP helper had the same defect, fixed in
commit 2b413fc689ba ("netfilter: nf_conntrack_ftp: avoid u16
overflows"). Apply the equivalent fix here: widen the port accumulator
to u32 and reject values above 65535, and reject address octets above
255.

## Which versions are affected by CVE-2026-90141?


## How do I fix CVE-2026-90141?

Apply the vendor's patch.

## Is CVE-2026-90141 being exploited?

There is no known exploitation of CVE-2026-90141 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90141 and fix it if it is affected.

What it is: CVE-2026-90141 is a high-severity vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90141 in the wild and no public exploit code.

Affected product: Linux. 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-2026-90141/ (Markdown: https://insights.sbomify.com/CVE-2026-90141/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90141
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90141
- OSV: https://osv.dev/vulnerability/CVE-2026-90141

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90141/
Summaries are generated and may contain mistakes; the official description above is the record.