CVE-2026-74697
Description
A flaw was found in the Linux kernel's bnxt_en driver. This vulnerability occurs when End of frame padding (EOP) on the AGG ring overlaps with subsequent data segments. On older network chips, if Relaxed Ordering (RO) is active, this overlap can cause valid data to be overwritten with zeros. This can lead to data corruption, impacting the integrity of information processed by the system.
Statement
bnxt_en can corrupt received packet data when EOP (End of frame padding) is used on AGG RX rings together with TPA and Relaxed Ordering. Zero padding at the end of one segment can overlap with data from the next segment, and on older chips such as P5 the hardware does not automatically disable Relaxed Ordering to prevent this. A remote peer may be able to influence the affected receive path by sending traffic to the Broadcom NIC, but practical triggering depends on specific hardware, ARM or ordering behavior, TPA being enabled, and RO being active. For the CVSS the PR:N is selected because the attacker does not need a local account when the vulnerable receive path is reachable by network traffic. Impact is primarily integrity loss due to corrupted received data and possible availability degradation, not a proven privilege escalation or information disclosure.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.8 | N/A | 8.2 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | Low | N/A | High |
| Availability Impact | High | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.