In the Linux kernel, the following vulnerability has been resolved: phonet/pep: disable BH around forwarded sk_receive_skb() The networking receive… (CVE-2026-64177)
A vulnerability in the Linux kernel's phonet/pep networking code involves inconsistent lock state handling around forwarded sk_receive_skb() calls. This can lead to a self-deadlock when bottom halves (BH) are enabled inconsistently during socket lock acquisition. The issue arises because the child socket lock is acquired with BH enabled in process context but with BH disabled in softirq context, causing lockdep warnings and potential deadlocks. The fix involves wrapping the forwarded sk_receive_skb() call with local_bh_disable() and local_bh_enable() to ensure consistent BH state.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel phonet/pep module is due to inconsistent bottom half (BH) state handling when forwarding packets to child sockets via sk_receive_skb(). In process context, BH is enabled when acquiring the child socket lock, whereas in softirq context BH is disabled. This inconsistency leads to lockdep warnings and can cause self-deadlocks if a softirq attempts to receive on the same child socket while the lock is held with BH enabled. The resolution is to disable BH around the forwarded sk_receive_skb() call, ensuring the child socket lock is always acquired with BH off. This fix prevents the inconsistent lock state and potential deadlocks. The issue was discovered via syzkaller fuzzing and reproduced with KASAN, LOCKDEP, and PROVE_LOCKING.
Potential Impact
The vulnerability can cause self-deadlocks in the Linux kernel networking stack when processing packets on phonet/pep sockets. This may lead to kernel hangs or degraded networking functionality on affected systems. There is no indication of remote code execution or privilege escalation. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented that wraps the forwarded sk_receive_skb() call with local_bh_disable() and local_bh_enable() to ensure consistent bottom half state during socket lock acquisition. Users should apply the official Linux kernel patch that addresses this issue. Since this is a kernel-level fix, upgrading to a kernel version containing this patch is the recommended remediation. Patch status is not explicitly provided here; check the vendor or Linux kernel mailing lists for the official fixed version.
In the Linux kernel, the following vulnerability has been resolved: phonet/pep: disable BH around forwarded sk_receive_skb() The networking receive… (CVE-2026-64177)
Description
A vulnerability in the Linux kernel's phonet/pep networking code involves inconsistent lock state handling around forwarded sk_receive_skb() calls. This can lead to a self-deadlock when bottom halves (BH) are enabled inconsistently during socket lock acquisition. The issue arises because the child socket lock is acquired with BH enabled in process context but with BH disabled in softirq context, causing lockdep warnings and potential deadlocks. The fix involves wrapping the forwarded sk_receive_skb() call with local_bh_disable() and local_bh_enable() to ensure consistent BH state.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel phonet/pep module is due to inconsistent bottom half (BH) state handling when forwarding packets to child sockets via sk_receive_skb(). In process context, BH is enabled when acquiring the child socket lock, whereas in softirq context BH is disabled. This inconsistency leads to lockdep warnings and can cause self-deadlocks if a softirq attempts to receive on the same child socket while the lock is held with BH enabled. The resolution is to disable BH around the forwarded sk_receive_skb() call, ensuring the child socket lock is always acquired with BH off. This fix prevents the inconsistent lock state and potential deadlocks. The issue was discovered via syzkaller fuzzing and reproduced with KASAN, LOCKDEP, and PROVE_LOCKING.
Potential Impact
The vulnerability can cause self-deadlocks in the Linux kernel networking stack when processing packets on phonet/pep sockets. This may lead to kernel hangs or degraded networking functionality on affected systems. There is no indication of remote code execution or privilege escalation. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented that wraps the forwarded sk_receive_skb() call with local_bh_disable() and local_bh_enable() to ensure consistent bottom half state during socket lock acquisition. Users should apply the official Linux kernel patch that addresses this issue. Since this is a kernel-level fix, upgrading to a kernel version containing this patch is the recommended remediation. Patch status is not explicitly provided here; check the vendor or Linux kernel mailing lists for the official fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-g3fg-4885-2jhq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64177"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912a24c
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:40:52 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.