Answer in brief
CVE-2026-97957 records a High severity (CVSS 8.8) vulnerability in net: hinic: fix mailbox segment buffer overflow. 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.
CVSS is 8.8. 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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c <eca54a092d5f7b497b458ff5a6f66d4f7bfb6674 || >=a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c <9f6ad383901d0cb1c8ea5f7f3160fabfe1540eb5 || >=a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c <513f7b16ed0cffae9348151c72bed17c7073096f || >=a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c <5d4d985957434867bbe85e4fa5e638f3e48ad522 | eca54a092d5f7b497b458ff5a6f66d4f7bfb6674, 9f6ad383901d0cb1c8ea5f7f3160fabfe1540eb5, 513f7b16ed0cffae9348151c72bed17c7073096f, 5d4d985957434867bbe85e4fa5e638f3e48ad522 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: net: hinic: fix mailbox segment buffer overflow check_mbox_seq_id_and_seg_len() validates that seq_id does not exceed SEQ_ID_MAX_VAL (42) and seg_len does not exceed MBOX_SEG_LEN (48). However, this allows the last segment (seq_id=42) to carry a full 48-byte payload, writing to offset 42*48=2016 for 48 bytes (ending at byte 2064). The receive buffer is only MBOX_MAX_BUF_SZ (2048) bytes, resulting in a 16-byte heap buffer overflow. The hinic3 driver already handles this correctly by defining MBOX_LAST_SEG_MAX_LEN and rejecting the last segment when it exceeds the remaining buffer space. Apply the same fix to the hinic driver.
Quoted source text, attributed separately from HOL analysis.