# CVE-2026-90145: hinic3: Fix skb linearization mismatch and drop skb when skb_checksum_help() failed

> 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.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-90145, DEBIAN-CVE-2026-90145, GHSA-x4f5-mm27-f75x, UBUNTU-CVE-2026-90145

## What is CVE-2026-90145?

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.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

hinic3: Fix skb linearization mismatch and drop skb when skb_checksum_help() failed

Previously, hinic3_send_one_skb() cached the skb fragment count before
calling hinic3_tx_offload(). If hinic3_tx_csum() falls back to
skb_checksum_help() for unsupported tunnel packets, the skb may be
linearized. Continuing to build the TX descriptor with the stale
fragment count leads to a descriptor mismatch, which can trigger
out-of-bounds DMA reads or IOMMU faults.

Furthermore, the old code ignored the return value of skb_checksum_help(),
transmitting corrupted packets with incomplete checksums upon failure.

Fix this by:
1. Moving the hinic3_tx_offload() call before calculating 'num_sge' to
   ensure the correct fragment count is used if the SKB is linearized.
2. Propagating skb_checksum_help() errors and returning
   HINIC3_TX_OFFLOAD_INVALID to properly drop the skb.

## Which versions are affected by CVE-2026-90145?


## How do I fix CVE-2026-90145?

Apply the vendor's patch.

## Is CVE-2026-90145 being exploited?

There is no known exploitation of CVE-2026-90145 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90145 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-90145 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90145/ (Markdown: https://insights.sbomify.com/CVE-2026-90145/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90145
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90145
- OSV: https://osv.dev/vulnerability/CVE-2026-90145

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90145/
Summaries are generated and may contain mistakes; the official description above is the record.