Local system hang via inconsistent child-socket locking
Published Jul 19, 2026 · Updated Jul 19, 2026
Deadlock in affected Linux Kernel releases allows local users to hang the system through Phonet PEP child-socket packet delivery. pep_do_rcv() forwards an inbound packet to a child socket via sk_receive_skb() while bottom halves can remain enabled, so the same socket lock is acquired in incompatible process and softirq states. Low-privileged local access and a same-CPU softirq race are required; successful exploitation self-deadlocks the kernel receive path and interrupts system availability.
Summary
What happened
Deadlock in affected Linux Kernel releases allows local users to hang the system through Phonet PEP child-socket packet delivery. pep_do_rcv() forwards an inbound packet to a child socket via sk_receive_skb() while bottom halves can remain enabled, so the same socket lock is acquired in incompatible process and softirq states. Low-privileged local access and a same-CPU softirq race are required; successful exploitation self-deadlocks the kernel receive path and interrupts system availability.
The record
- CVE
- CVE-2026-64177
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-833, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=2.6.28
- Affected versionversion=9641458d3ec42def729fde64669abf07f3220cd5 <02c04df84de709060f63e1d52ec67488c4f6f212
- Affected versionversion=9641458d3ec42def729fde64669abf07f3220cd5 <8420aa4900417797323dd567ba9d1512280c2dc3
- Affected versionversion=9641458d3ec42def729fde64669abf07f3220cd5 <84bc87beb4cd77670939b446326788e4c9b3db37
- Affected versionversion=9641458d3ec42def729fde64669abf07f3220cd5 <a3fc8f2dacd1c37325977fc1fbbf3d52141df99e
- Affected versionversion=9641458d3ec42def729fde64669abf07f3220cd5 <b2606c302d7f2b4ee48da05e32ed60aed1b0cd53
- Affected versionversion=9641458d3ec42def729fde64669abf07f3220cd5 <bd795f106b3889fb0706c6e4831c4b27e2b5666b
- Affected versionversion=9641458d3ec42def729fde64669abf07f3220cd5 <dbc81608e3a653dea6cf403f20cae35468b8ab9c
- Affected versionversion=9641458d3ec42def729fde64669abf07f3220cd5 <f08c45076e4fd8b0adbc5eb186d6e6a3e7350d7b
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
- Syzkaller reproducer for the Phonet PEP deadlockproof of concept · demonstrated
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