hinic3: Fix skb linearization mismatch and drop skb when skb_checksum_help() failed
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d · fixed in e794cdc5c369c1b06359e2fe03a8d9270f56bead; From 17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d · fixed in 96c3959770386b2913c62005f0d0c3151e0c01c3; From 17fcb3dc12bbee8ec3e32ca1f60898f252e06b2d · fixed in d0c2bed6927cbfa2cb51f240b4812bf6916bce0e
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6