Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97957net: hinic: fix mailbox segment buffer overflow

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-97957, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 96% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c – < 7cc974799fde846eda2d8f00ad4f8e1810eb0499
    • affected a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c – < 8de1e23bd91fe3a6683e4bc574e2d6bcb0eef920
    • affected a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c – < 72be1fd5d256dde748c0905c5e1749a119cad5bd
    • affected a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c – < c622bbc212207d7c6bbd69dd88f0c3a3f5853d16
    • affected a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c – < eca54a092d5f7b497b458ff5a6f66d4f7bfb6674
    • affected a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c – < 9f6ad383901d0cb1c8ea5f7f3160fabfe1540eb5
    • affected a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c – < 513f7b16ed0cffae9348151c72bed17c7073096f
    • affected a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c – < 5d4d985957434867bbe85e4fa5e638f3e48ad522
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97957 badge
[![CVE-2026-97957](https://cveledger.app/badge/CVE-2026-97957.svg)](https://cveledger.app/cve/CVE-2026-97957)

Record last updated .