{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90145 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90145 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90145 and fix it if it is affected.\n\nWhat it is: CVE-2026-90145 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90145 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-90145/ (Markdown: https://insights.sbomify.com/CVE-2026-90145/index.md)","id":"CVE-2026-90145","markdown":"https://insights.sbomify.com/CVE-2026-90145/index.md","name":"CVE-2026-90145","record":{"aliases":["BELL-CVE-2026-90145","DEBIAN-CVE-2026-90145","GHSA-x4f5-mm27-f75x","UBUNTU-CVE-2026-90145"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A flaw in the hinic3 network driver allows out-of-bounds DMA reads or IOMMU faults due to stale fragment counts, potentially causing system crashes or information disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhinic3: Fix skb linearization mismatch and drop skb when skb_checksum_help() failed\n\nPreviously, hinic3_send_one_skb() cached the skb fragment count before\ncalling hinic3_tx_offload(). If hinic3_tx_csum() falls back to\nskb_checksum_help() for unsupported tunnel packets, the skb may be\nlinearized. Continuing to build the TX descriptor with the stale\nfragment count leads to a descriptor mismatch, which can trigger\nout-of-bounds DMA reads or IOMMU faults.\n\nFurthermore, the old code ignored the return value of skb_checksum_help(),\ntransmitting corrupted packets with incomplete checksums upon failure.\n\nFix this by:\n1. Moving the hinic3_tx_offload() call before calculating 'num_sge' to\n   ensure the correct fragment count is used if the SKB is linearized.\n2. Propagating skb_checksum_help() errors and returning\n   HINIC3_TX_OFFLOAD_INVALID to properly drop the skb.","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":"hinic3: Fix skb linearization mismatch and drop skb when skb_checksum_help() failed","id":"CVE-2026-90145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"bpf, xdp: move offload check into dev_xdp_install()","id":"CVE-2026-90146"},"packages":[],"prev":{"headline":"dpll: fix NULL deref in dpll_device_ops() during teardown race","id":"CVE-2026-90144"},"products":["Linux"],"published":"2026-09-17","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-10-19","vendors":["Linux"]},"summary":"A flaw in the hinic3 network driver allows out-of-bounds DMA reads or IOMMU faults due to stale fragment counts, potentially causing system crashes or information disclosure.","url":"https://insights.sbomify.com/CVE-2026-90145/"}