Local memory corruption via stale control-socket pointer
Published Jun 23, 2026 · Updated Jun 23, 2026
Heap use-after-free in dhcpcd 10.3.2 and earlier allows local users to corrupt memory through the control socket. control_recvdata() frees the client object after a privileged command error, but a combined READ and HANGUP event then passes the stale pointer to control_hangup(). Reachability requires disabled or failed privilege separation with a mode 0666 control socket; triggering corrupts daemon memory and can interrupt network configuration.
Summary
What happened
Heap use-after-free in dhcpcd 10.3.2 and earlier allows local users to corrupt memory through the control socket. control_recvdata() frees the client object after a privileged command error, but a combined READ and HANGUP event then passes the stale pointer to control_hangup(). Reachability requires disabled or failed privilege separation with a mode 0666 control socket; triggering corrupts daemon memory and can interrupt network configuration.
The record
- CVE
- CVE-2026-56117
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Network Configuration
- Product
- dhcpcd
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=10.3.2
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo