{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40337 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40337 is a high-severity vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40337 and fix it if it is affected.\n\nWhat it is: CVE-2025-40337 is a high-severity vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40337 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-2025-40337/ (Markdown: https://insights.sbomify.com/CVE-2025-40337/index.md)","id":"CVE-2025-40337","markdown":"https://insights.sbomify.com/CVE-2025-40337/index.md","name":"CVE-2025-40337","record":{"aliases":["BELL-CVE-2025-40337","DEBIAN-CVE-2025-40337","GHSA-4h2c-rg8h-8jqc","ROOT-OS-DEBIAN-11-CVE-2025-40337","ROOT-OS-DEBIAN-12-CVE-2025-40337","ROOT-OS-DEBIAN-13-CVE-2025-40337","ROOT-OS-UBUNTU-2204-CVE-2025-40337","ROOT-OS-UBUNTU-2404-CVE-2025-40337","UBUNTU-CVE-2025-40337"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel network driver","requires_auth":"none","summary":"The stmmac driver ignored hardware checksum errors, allowing corrupt packets to be treated as valid, potentially leading to data integrity issues.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","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\nnet: stmmac: Correctly handle Rx checksum offload errors\n\nThe stmmac_rx function would previously set skb-\u003eip_summed to\nCHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled\nand the packet was of a known IP ethertype.\n\nHowever, this logic failed to check if the hardware had actually\nreported a checksum error. The hardware status, indicating a header or\npayload checksum failure, was being ignored at this stage. This could\ncause corrupt packets to be passed up the network stack as valid.\n\nThis patch corrects the logic by checking the `csum_none` status flag,\nwhich is set when the hardware reports a checksum error. If this flag\nis set, skb-\u003eip_summed is now correctly set to CHECKSUM_NONE,\nensuring the kernel's network stack will perform its own validation and\nproperly handle the corrupt packet.","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":"net: stmmac: Correctly handle Rx checksum offload errors","id":"CVE-2025-40337","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"ASoC: Intel: avs: Do not share the name pointer between components","id":"CVE-2025-40338"},"packages":[],"prev":{"headline":"drm/gpusvm: fix hmm_pfn_to_map_order() usage","id":"CVE-2025-40336"},"products":["Linux"],"published":"2025-12-09","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"The stmmac driver ignored hardware checksum errors, allowing corrupt packets to be treated as valid, potentially leading to data integrity issues.","url":"https://insights.sbomify.com/CVE-2025-40337/"}