VulnerabilityPublished 22 Aug 2026Updated 21 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited · CVSS 8.2 High · fixed in c1962ab4645a914a91ff492735881150ddc8a79e : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS

0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers can reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch

Available – fixed in c1962ab4645a914a91ff492735881150ddc8a79e, c3faf548a00f4c17100cc9204746975fa46a73b9, b61c4911204a0a2f900e538d64ceb608f6c9614d +5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bfcd8d791ec18496772d117774398e336917f56e, < c1962ab4645a914a91ff492735881150ddc8a79e	Fixed in c1962ab4645a914a91ff492735881150ddc8a79e
LinuxLinux	Affected ≥ bfcd8d791ec18496772d117774398e336917f56e, < c3faf548a00f4c17100cc9204746975fa46a73b9	Fixed in c3faf548a00f4c17100cc9204746975fa46a73b9
LinuxLinux	Affected ≥ bfcd8d791ec18496772d117774398e336917f56e, < b61c4911204a0a2f900e538d64ceb608f6c9614d	Fixed in b61c4911204a0a2f900e538d64ceb608f6c9614d
LinuxLinux	Affected ≥ bfcd8d791ec18496772d117774398e336917f56e, < aab3b5f4d8ec8598606ee011e219ef824ae25ca0	Fixed in aab3b5f4d8ec8598606ee011e219ef824ae25ca0
LinuxLinux	Affected ≥ bfcd8d791ec18496772d117774398e336917f56e, < 927e2617a36f49752cb5613900ca21f40593f07d	Fixed in 927e2617a36f49752cb5613900ca21f40593f07d
LinuxLinux	Affected ≥ bfcd8d791ec18496772d117774398e336917f56e, < 410da4428b1f47bf9a84bdc0bcaa089d73ba2048	Fixed in 410da4428b1f47bf9a84bdc0bcaa089d73ba2048

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.

References

Community reviews

Loading reviews…