# CVE-2026-72041: espintcp: use sk_msg_free_partial to fix partial send

> A bug in Linux kernel ESP-in-TCP handling caused incorrect memory accounting during partial sends, potentially leading to resource inconsistencies.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-72041, DEBIAN-CVE-2026-72041, GHSA-55rh-f38r-fhcc, UBUNTU-CVE-2026-72041

## What is CVE-2026-72041?

CVE-2026-72041 is a critical vulnerability in Linux, published on 15 Aug 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:

espintcp: use sk_msg_free_partial to fix partial send

sk_msg_free_partial() ensures consistency of the skmsg at every
iteration, without having to manually handle uncharges and offsets.
This simplifies the code, and fixes some bugs in skmsg accounting when
we don't send the full contents.

Weakness: CWE-664 (Improper Control of a Resource Through its Lifetime)

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


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

Apply the vendor's patch.

## Is CVE-2026-72041 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72041 is a critical vulnerability in Linux, published on 15 Aug 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-72041 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-72041/ (Markdown: https://insights.sbomify.com/CVE-2026-72041/index.md)
```

## Sources

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

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