{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74697 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-74697 is a high-severity vulnerability in Linux, published on 22 Aug 2026."},"fix_prompt":"Check this codebase for CVE-2026-74697 and fix it if it is affected.\n\nWhat it is: CVE-2026-74697 is a high-severity vulnerability in Linux, published on 22 Aug 2026. \nExploitation: There is no known exploitation of CVE-2026-74697 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74697/ (Markdown: https://insights.sbomify.com/CVE-2026-74697/index.md)","id":"CVE-2026-74697","markdown":"https://insights.sbomify.com/CVE-2026-74697/index.md","name":"CVE-2026-74697","record":{"aliases":["AZL-97104","BELL-CVE-2026-74697","DEBIAN-CVE-2026-74697","GHSA-fmvg-rgc2-qx29","UBUNTU-CVE-2026-74697"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbnxt_en: Disable EOP for TPA on all chips to prevent data corruption\n\nEOP (End of frame padding) on the AGG ring may cause overlapping of\nzero padding at the end of one segment with the next segment's data.\nIf Relaxed Ordering (RO) is enabled, the zero padding may overwrite\nvalid data in the next segment and corrupt the data.  Older chips\n(P5 and older) do not automatically disable RO when EOP is enabled.\nOn some ARM systems, data corruption was reported on 57508 (P5)\nchips with RO enabled.\n\nAlways disable EOP on all chips on the AGG rings when TPA is enabled\nto fix the data corruption.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"bnxt_en: Disable EOP for TPA on all chips to prevent data corruption","id":"CVE-2026-74697","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"net/mlx5e: fix BQL reset on SQ re-activation","id":"CVE-2026-74698"},"packages":[],"prev":{"headline":"tcp: fix TFO max_qlen accounting across reuseport migration","id":"CVE-2026-74696"},"products":["Linux"],"published":"2026-08-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-74697/"}