CVE-2026-97957
Received Received - Intake

Heap Buffer Overflow in Linux Kernel Hinic Driver

Vulnerability report for CVE-2026-97957, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-25

Last updated on: 2026-09-25

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-25
Last Modified
2026-09-25
Generated
2026-09-25
AI Q&A
2026-09-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a heap buffer overflow vulnerability in the Linux kernel's hinic network driver. It occurs when processing mailbox messages where the sequence ID and segment length are not properly validated. The last segment can write 48 bytes beyond the intended 2048-byte buffer limit, causing a 16-byte overflow.

Detection Guidance

This vulnerability is specific to the Linux kernel's hinic driver and involves a heap buffer overflow in mailbox handling. Detection requires checking the kernel version and hinic driver configuration. Commands like 'uname -a' to check kernel version and 'lsmod | grep hinic' to verify if the driver is loaded may help. Monitor system logs for crashes or memory corruption errors related to the hinic driver.

Impact Analysis

This vulnerability could allow an attacker with local access to cause memory corruption, potentially leading to system crashes, privilege escalation, or arbitrary code execution. It may also enable denial-of-service conditions on affected systems.

Mitigation Strategies

Apply the latest kernel update that includes the fix for this vulnerability. If using a distribution-specific kernel, check for patches from your vendor. Temporarily disable the hinic driver if not in use by blacklisting it. Monitor vendor advisories for updates and test patches in a non-production environment before full deployment.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-97957. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart