# CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame

> An out-of-bounds write in the enetc network driver allows attackers to cause memory corruption, potentially leading to system crashes or code execution.

- **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:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72399, DEBIAN-CVE-2026-72399, GHSA-5679-m6c7-f7x8, UBUNTU-CVE-2026-72399

## What is CVE-2026-72399?

CVE-2026-72399 is a critical memory corruption 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:

net: enetc: check the number of BDs needed for xdp_frame

The size of xdp_redirect_arr array is ENETC_MAX_SKB_FRAGS. However, the
number of fragments contained in xdp_frame may be greater than or equal
to ENETC_MAX_SKB_FRAGS, which will cause the access to xdp_redirect_arr
to be out of bounds.

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


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

Apply the vendor's patch.

## Is CVE-2026-72399 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72399 is a critical memory corruption 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-72399 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-72399/ (Markdown: https://insights.sbomify.com/CVE-2026-72399/index.md)
```

## Sources

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

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