CVE-2026-74697

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (7)

Auto-updated Aug 25, 2026
No patch confirmed yet.
generic

bnxt_en: Disable EOP for TPA on all chips to prevent data corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3faf548a00f4c17100cc9204746975fa46a73b9
generic

bnxt_en: Disable EOP for TPA on all chips to prevent data corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c1962ab4645a914a91ff492735881150ddc8a79e
generic

bnxt_en: Disable EOP for TPA on all chips to prevent data corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aab3b5f4d8ec8598606ee011e219ef824ae25ca0
generic

bnxt_en: Disable EOP for TPA on all chips to prevent data corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b61c4911204a0a2f900e538d64ceb608f6c9614d
generic

bnxt_en: Disable EOP for TPA on all chips to prevent data corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/410da4428b1f47bf9a84bdc0bcaa089d73ba2048
generic

bnxt_en: Disable EOP for TPA on all chips to prevent data corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7aee22a35978b44784612c156e358e375ddf5d16
generic

bnxt_en: Disable EOP for TPA on all chips to prevent data corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68c181af7cd1ca9cbf29acd95911073bfd3c6397

Vendor Advisories for CVE-2026-74697(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 25× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 22:29 UTCGHSA enrichment
  3. 2026-08-29 11:36 UTCGHSA enrichment
  4. 2026-08-29 00:40 UTCEG score recompute
  5. 2026-08-29 00:39 UTCGHSA enrichment
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 10:37 UTCGHSA enrichment
  8. 2026-08-27 23:45 UTCEG score recompute
  9. 2026-08-27 23:45 UTCGHSA enrichment
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 12:53 UTCGHSA enrichment
  12. 2026-08-27 02:00 UTCGHSA enrichment
  13. 2026-08-26 15:08 UTCEG score recompute
  14. 2026-08-26 15:08 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 04:15 UTCGHSA enrichment
  17. 2026-08-25 17:21 UTCEG score recompute
  18. 2026-08-25 17:21 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:29 UTCEG score recompute
  21. 2026-08-25 06:29 UTCGHSA enrichment
  22. 2026-08-25 05:55 UTCEG score recompute▲ 8.20
  23. 2026-08-25 05:55 UTCGHSA enrichment
  24. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 8.2 · severity → HIGH
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 3 more
  1. 2026-08-22 16:24 UTCNVD update
  2. 2026-08-22 15:39 UTCEG score recompute
  3. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74697?
CVE-2026-74697 is a high vulnerability published on August 22, 2026. 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)…
When was CVE-2026-74697 disclosed?
CVE-2026-74697 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74697 actively exploited?
CVE-2026-74697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.0% of all scored CVEs.
What is the CVSS score of CVE-2026-74697?
CVE-2026-74697 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-74697?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74697, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74697

Explore →

Is Your Infrastructure Affected by CVE-2026-74697?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs