# CVE-2026-74697: bnxt_en: Disable EOP for TPA on all chips to prevent data corruption


- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-97104, BELL-CVE-2026-74697, DEBIAN-CVE-2026-74697, GHSA-fmvg-rgc2-qx29, UBUNTU-CVE-2026-74697

## What is CVE-2026-74697?

CVE-2026-74697 is a high-severity vulnerability in Linux, published on 22 Aug 2026. 

### Official description

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

bnxt_en: Disable EOP for TPA on all chips to prevent data corruption

EOP (End of frame padding) on the AGG ring may cause overlapping of
zero padding at the end of one segment with the next segment's data.
If Relaxed Ordering (RO) is enabled, the zero padding may overwrite
valid data in the next segment and corrupt the data.  Older chips
(P5 and older) do not automatically disable RO when EOP is enabled.
On some ARM systems, data corruption was reported on 57508 (P5)
chips with RO enabled.

Always disable EOP on all chips on the AGG rings when TPA is enabled
to fix the data corruption.

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


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

Upgrade to a fixed version.

## Is CVE-2026-74697 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74697 is a high-severity vulnerability in Linux, published on 22 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-74697 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-74697/ (Markdown: https://insights.sbomify.com/CVE-2026-74697/index.md)
```

## Sources

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

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