Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74697

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74697, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
NVDNVD · Received3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS (exploitation in 30 days)
0.45% · top 60% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

  • Linux · Linux

    • affected bfcd8d791ec18496772d117774398e336917f56e – < 68c181af7cd1ca9cbf29acd95911073bfd3c6397
    • affected bfcd8d791ec18496772d117774398e336917f56e – < 7aee22a35978b44784612c156e358e375ddf5d16
    • affected bfcd8d791ec18496772d117774398e336917f56e – < 410da4428b1f47bf9a84bdc0bcaa089d73ba2048
    • affected bfcd8d791ec18496772d117774398e336917f56e – < b61c4911204a0a2f900e538d64ceb608f6c9614d
    • affected bfcd8d791ec18496772d117774398e336917f56e – < 927e2617a36f49752cb5613900ca21f40593f07d
    • affected bfcd8d791ec18496772d117774398e336917f56e – < aab3b5f4d8ec8598606ee011e219ef824ae25ca0
    • affected bfcd8d791ec18496772d117774398e336917f56e – < c1962ab4645a914a91ff492735881150ddc8a79e
    • affected bfcd8d791ec18496772d117774398e336917f56e – < c3faf548a00f4c17100cc9204746975fa46a73b9
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.152 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.45 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74697 badge
[![CVE-2026-74697](https://cveledger.app/badge/CVE-2026-74697.svg)](https://cveledger.app/cve/CVE-2026-74697)

Record last updated .