PT-2026-61494 · Linux · Linux Kernel
CVE-2026-64177
·
Published
2026-07-19
·
Updated
2026-07-19
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
Name of the Vulnerable Software and Affected Versions
Linux kernel (affected versions not specified)
Description
An inconsistent lock state exists in the networking receive path when handling PEP pipes. When an inbound socket buffer (skb) targets an existing PEP pipe, the
pep do rcv() function forwards the skb to a child socket using sk receive skb(). This process utilizes bh lock sock nested(), which assumes that bottom halves (BH) are already disabled. However, if the process is running in process context, the child socket lock may be acquired while BH is enabled, whereas in the softirq context, it is acquired with BH disabled. This inconsistency can lead to a self-deadlock if a softirq on the same CPU attempts to receive data for the same child socket while the lock is held in the BH-enabled path.Recommendations
At the moment, there is no information about a newer version that contains a fix for this vulnerability.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux Kernel