Host-process crash via undersized reply buffers
Published Sep 22, 2026 · Updated Sep 22, 2026
Heap buffer overflow in libslirp's DHCPv6 and TFTP reply builders allows guest OS users to crash the host process with crafted options. The builders copy attacker-controlled option content and length into a reply buffer sized for a small interface MTU without rejecting the oversized response. A nondefault small MTU is required; resulting heap corruption also permits arbitrary code execution in the host process.
Summary
What happened
Heap buffer overflow in libslirp's DHCPv6 and TFTP reply builders allows guest OS users to crash the host process with crafted options. The builders copy attacker-controlled option content and length into a reply buffer sized for a small interface MTU without rejecting the oversized response. A nondefault small MTU is required; resulting heap corruption also permits arbitrary code execution in the host process.
The record
- CVE
- CVE-2026-95508
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- Commonhaus Foundation
- Product
- Red Hat Enterprise Linux 10
- Classifications
- T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started