CVE-2026-74697
Linux bnxt_en NIC driver bug can corrupt received packet data.
Is CVE-2026-74697 being exploited?
Not confirmed. CVE-2026-74697 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-74697?
CVE-2026-74697 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74697?
Yes. A fix has been recorded for CVE-2026-74697. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74697 affect?
CVE-2026-74697 affects Linux kernel (bnxt_en driver), Broadcom NetXtreme-E (bnxt) NICs — P5/57508 chips, Servers and ARM systems using affected NICs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74697?
Apply vendor/kernel bnxt_en patch immediately; disable TPA/EOP on bnxt NICs until updated.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote network traffic can trigger the bnxt_en driver to overwrite adjacent packet segments, causing payload corruption, data loss, and application-level failures.
Immediate action required
- affected>= bfcd8d791ec18496772d117774398e336917f56e and < 68c181af7cd1ca9cbf29acd95911073bfd3c6397
- affected>= bfcd8d791ec18496772d117774398e336917f56e and < 7aee22a35978b44784612c156e358e375ddf5d16
- affected>= bfcd8d791ec18496772d117774398e336917f56e and < 410da4428b1f47bf9a84bdc0bcaa089d73ba2048
- affected>= bfcd8d791ec18496772d117774398e336917f56e and < b61c4911204a0a2f900e538d64ceb608f6c9614d
- affected>= bfcd8d791ec18496772d117774398e336917f56e and < aab3b5f4d8ec8598606ee011e219ef824ae25ca0
- affected>= bfcd8d791ec18496772d117774398e336917f56e and < c1962ab4645a914a91ff492735881150ddc8a79e
- affected>= bfcd8d791ec18496772d117774398e336917f56e and < c3faf548a00f4c17100cc9204746975fa46a73b9
- affected5.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.