CVE-2026-97957: net: hinic: fix mailbox segment buffer overflow
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 513f7b16ed0cffae9348151c72bed17c7073096f, 5d4d985957434867bbe85e4fa5e638f3e48ad522, 72be1fd5d256dde748c0905c5e1749a119cad5bd; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 513f7b16ed0cffae9348151c72bed17c7073096f, 5d4d985957434867bbe85e4fa5e638f3e48ad522, 72be1fd5d256dde748c0905c5e1749a119cad5bd; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.8affected
- a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c and later · before 7cc974799fde846eda2d8f00ad4f8e1810eb0499affected · git
- a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c and later · before 8de1e23bd91fe3a6683e4bc574e2d6bcb0eef920affected · git
- a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c and later · before 72be1fd5d256dde748c0905c5e1749a119cad5bdaffected · git
- a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c and later · before c622bbc212207d7c6bbd69dd88f0c3a3f5853d16affected · git
- a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c and later · before eca54a092d5f7b497b458ff5a6f66d4f7bfb6674affected · git
- a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c and later · before 9f6ad383901d0cb1c8ea5f7f3160fabfe1540eb5affected · git
- a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c and later · before 513f7b16ed0cffae9348151c72bed17c7073096faffected · git
- a425b6e1c69ba907b72b737a4d44f8cfbc43ce3c and later · before 5d4d985957434867bbe85e4fa5e638f3e48ad522affected · git
- before 5.8not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97955Sep 25, 2026 · net: mana: restore the XDP program pointer when pre-allocation fails0Monitor
- ← EarlierCVE-2026-97956Sep 25, 2026 · net: net_failover: Fix the deadlock in net_failover_slave_name_change()0Monitor
- Later →CVE-2026-97958Sep 25, 2026 · net/sched: cls_api: Don't replay RTM_GETCHAIN in tc_ctl_chain().0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 513f7b16ed0cffae9348151c72bed17c7073096f | Vendor (CNA) |
| Linux Linux | 5d4d985957434867bbe85e4fa5e638f3e48ad522 | Vendor (CNA) |
| Linux Linux | 72be1fd5d256dde748c0905c5e1749a119cad5bd | Vendor (CNA) |
| Linux Linux | 7cc974799fde846eda2d8f00ad4f8e1810eb0499 | Vendor (CNA) |
| Linux Linux | 8de1e23bd91fe3a6683e4bc574e2d6bcb0eef920 | Vendor (CNA) |
| Linux Linux | 9f6ad383901d0cb1c8ea5f7f3160fabfe1540eb5 | Vendor (CNA) |
| Linux Linux | c622bbc212207d7c6bbd69dd88f0c3a3f5853d16 | Vendor (CNA) |
| Linux Linux | eca54a092d5f7b497b458ff5a6f66d4f7bfb6674 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5d4d985957434867bbe85e4fa5e638f3e48ad522
- git.kernel.org/stable/c/72be1fd5d256dde748c0905c5e1749a119cad5bd
- git.kernel.org/stable/c/7cc974799fde846eda2d8f00ad4f8e1810eb0499
- git.kernel.org/stable/c/8de1e23bd91fe3a6683e4bc574e2d6bcb0eef920
- git.kernel.org/stable/c/9f6ad383901d0cb1c8ea5f7f3160fabfe1540eb5
- git.kernel.org/stable/c/c622bbc212207d7c6bbd69dd88f0c3a3f5853d16
- git.kernel.org/stable/c/eca54a092d5f7b497b458ff5a6f66d4f7bfb6674
Vendor advisories and official records. Exploit/PoC links are deliberately left out.