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

Unknown severity · Source severity not reportedCVE-2026-90145

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

Answer in brief

CVE-2026-90145 records a Unknown severity vulnerability in hinic3: Fix skb linearization mismatch and drop skb when skb_checksum_help() failed. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d <e794cdc5c369c1b06359e2fe03a8d9270f56bead \|\| >=17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d <96c3959770386b2913c62005f0d0c3151e0c01c3 \|\| >=17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d <d0c2bed6927cbfa2cb51f240b4812bf6916bce0e	e794cdc5c369c1b06359e2fe03a8d9270f56bead, 96c3959770386b2913c62005f0d0c3151e0c01c3, d0c2bed6927cbfa2cb51f240b4812bf6916bce0e
Linux/Linuxgeneric	6.16	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to e794cdc5c369c1b06359e2fe03a8d9270f56bead if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

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

Quoted source text, attributed separately from HOL analysis.