cve-2026-64177
MEDIUM CVSS 5.5 opencve
Description
In the Linux kernel, the following vulnerability has been resolved: phonet/pep: disable BH around forwarded sk_receive_skb() The networking receive path is usually run from softirq context, but protocols that take the socket lock may have packets stored in the backlog and processed later from process context. In that case release_sock() -> __release_sock() drops the slock with spin_unlock_bh() and then calls sk->sk_backlog_rcv() with bottom halves enabled. Typical sk_backlog_rcv handlers process the socket whose backlog is being drained, so the BH state at entry is irrelevant for the slocks they touch. pep_do_rcv() is different: when the inbound skb targets an existing PEP pipe, it forwards the skb to a different *child* socket via sk_receive_skb(). That helper takes the child slock with bh_lock_sock_nested(), which is just spin_lock_nested() and assumes BH is already off. The same child slock therefore ends up acquired with BH on (process path) and with BH off (softirq path): process context softirq context --------------- --------------- release_sock(listener) __netif_receive_skb() __release_sock() phonet_rcv() spin_unlock_bh() __sk_receive_skb(listener) [BH now ENABLED] [BH already disabled] sk_backlog_rcv: sk_backlog_rcv: pep_do_rcv() pep_do_rcv() sk_receive_skb(child) sk_receive_skb(child) bh_lock_sock_nested(child) bh_lock_sock_nested(child) => SOFTIRQ-ON-W => IN-SOFTIRQ-W Lockdep flags this as inconsistent lock state, and it can become a real self-deadlock if a softirq on the same CPU tries to receive to the same child socket while its slock is held in the BH-enabled path: WARNING: inconsistent lock state inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage. (slock-AF_PHONET/1){+.?.}-{3:3}, at: __sk_receive_skb+0x1cf/0x900 __sk_receive_skb net/core/sock.c:563 sk_receive_skb include/net/sock.h:2022 [inline] pep_do_rcv net/phonet/pep.c:675 sk_backlog_rcv include/net/sock.h:1190 __release_sock net/core/sock.c:3216 release_sock net/core/sock.c:3815 pep_sock_accept net/phonet/pep.c:879 Wrap the forwarded sk_receive_skb() in local_bh_disable() / local_bh_enable() so the child slock is always acquired with BH off. local_bh_disable() nests safely on the softirq path. Discovered via in-house syzkaller fuzzing; the same root cause also on the linux-6.1.y syzbot dashboard as extid 44f0626dd6284f02663c. Reproduced under KASAN + LOCKDEP + PROVE_LOCKING, reproducer: https://pastebin.com/A3t8xzCR
Timeline
- Published
- 2026-07-19 16:17 UTC
- Last Modified
- 2026-08-13
CVSS Details
CVSS details not available.
Affected Products
No product information available.
Weaknesses (CWE)
CVSS metrics
| Version | Base | Severity | Vector | Exploitability | Impact | Source |
|---|---|---|---|---|---|---|
| 3.1 | 5.5 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
nvd | ||
| 3.1 | 5.5 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
opencve | ||
| 3.1 | 5.5 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
redhat |
References
No references available.
Linked Vulnerabilities
{
"advisories": [
{
"id": "USN-8575-1",
"source": "usn",
"title": "Linux kernel vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8575-1"
},
{
"id": "USN-8576-1",
"source": "usn",
"title": "Linux kernel (NVIDIA Tegra) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8576-1"
},
{
"id": "USN-8593-1",
"source": "usn",
"title": "Linux kernel vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8593-1"
},
{
"id": "USN-8575-2",
"source": "usn",
"title": "Linux kernel vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8575-2"
},
{
"id": "USN-8576-2",
"source": "usn",
"title": "Linux kernel (NVIDIA Tegra) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8576-2"
},
{
"id": "USN-8575-3",
"source": "usn",
"title": "Linux kernel vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8575-3"
},
{
"id": "USN-8603-1",
"source": "usn",
"title": "Linux kernel (Azure) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8603-1"
},
{
"id": "USN-8610-1",
"source": "usn",
"title": "Linux kernel (Azure CVM) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8610-1"
},
{
"id": "USN-8618-1",
"source": "usn",
"title": "Linux kernel vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8618-1"
},
{
"id": "USN-8620-1",
"source": "usn",
"title": "Linux kernel vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8620-1"
},
{
"id": "USN-8620-2",
"source": "usn",
"title": "Linux kernel (Azure FIPS) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8620-2"
},
{
"id": "USN-8620-3",
"source": "usn",
"title": "Linux kernel (Intel IoTG) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8620-3"
},
{
"id": "USN-8620-4",
"source": "usn",
"title": "Linux kernel (Intel IoTG) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8620-4"
},
{
"id": "USN-8663-1",
"source": "usn",
"title": "Linux kernel (NVIDIA) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8663-1"
},
{
"id": "USN-8664-1",
"source": "usn",
"title": "Linux kernel (NVIDIA BaseOS) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8664-1"
},
{
"id": "USN-8668-1",
"source": "usn",
"title": "Linux kernel (GCP) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8668-1"
},
{
"id": "USN-8728-1",
"source": "usn",
"title": "Linux kernel (GCP) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8728-1"
},
{
"id": "USN-8729-1",
"source": "usn",
"title": "Linux kernel vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8729-1"
},
{
"id": "USN-8761-1",
"source": "usn",
"title": "Linux kernel (Azure) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8761-1"
},
{
"id": "USN-8729-2",
"source": "usn",
"title": "Linux kernel (Raspberry Pi Real-time) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8729-2"
},
{
"id": "USN-8761-2",
"source": "usn",
"title": "Linux kernel (Azure FIPS) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8761-2"
},
{
"id": "USN-8781-1",
"source": "usn",
"title": "Linux kernel (NVIDIA Tegra) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8781-1"
},
{
"id": "USN-8668-2",
"source": "usn",
"title": "Linux kernel (Raspberry Pi) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8668-2"
},
{
"id": "USN-8729-3",
"source": "usn",
"title": "Linux kernel vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8729-3"
},
{
"id": "USN-8802-1",
"source": "usn",
"title": "Linux kernel (Oracle) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8802-1"
},
{
"id": "USN-8728-2",
"source": "usn",
"title": "Linux kernel (Azure) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8728-2"
},
{
"id": "USN-8729-4",
"source": "usn",
"title": "Linux kernel (Low Latency) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8729-4"
},
{
"id": "USN-8729-5",
"source": "usn",
"title": "Linux kernel (AWS FIPS) vulnerabilities",
"url": "https://ubuntu.com/security/notices/USN-8729-5"
}
],
"cve": "CVE-2026-64177",
"enrichment": {
"affected": [
{
"configurations": [
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "code_commit",
"value": "[9641458d3ec42def729fde64669abf07f3220cd5,f08c45076e4fd8b0adbc5eb186d6e6a3e7350d7b)"
}
},
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "code_commit",
"value": "[9641458d3ec42def729fde64669abf07f3220cd5,b2606c302d7f2b4ee48da05e32ed60aed1b0cd53)"
}
},
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "code_commit",
"value": "[9641458d3ec42def729fde64669abf07f3220cd5,02c04df84de709060f63e1d52ec67488c4f6f212)"
}
},
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "code_commit",
"value": "[9641458d3ec42def729fde64669abf07f3220cd5,8420aa4900417797323dd567ba9d1512280c2dc3)"
}
},
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "code_commit",
"value": "[9641458d3ec42def729fde64669abf07f3220cd5,bd795f106b3889fb0706c6e4831c4b27e2b5666b)"
}
},
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "code_commit",
"value": "[9641458d3ec42def729fde64669abf07f3220cd5,84bc87beb4cd77670939b446326788e4c9b3db37)"
}
},
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "code_commit",
"value": "[9641458d3ec42def729fde64669abf07f3220cd5,a3fc8f2dacd1c37325977fc1fbbf3d52141df99e)"
}
},
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "code_commit",
"value": "[9641458d3ec42def729fde64669abf07f3220cd5,dbc81608e3a653dea6cf403f20cae35468b8ab9c)"
}
}
],
"enrichment": {
"confidence": 99.0,
"confidence_source": "inferred",
"scores": [
{
"score": 99.0,
"source": "inferred"
},
{
"score": 100.0,
"source": "matching"
}
]
},
"original": {
"product": "Linux",
"source": "cna",
"vendor": "Linux"
},
"product": "linux_kernel",
"vendor": "linux"
},
{
"configurations": [
{
"platform": null,
"status": "affected",
"versions": {
"scheme": "semver",
"value": "2.6.28"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "semver",
"value": "[0,2.6.28)"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "semver",
"value": "[5.10.258,5.11.0)"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "semver",
"value": "[5.15.209,5.16.0)"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "semver",
"value": "[6.1.175,6.2.0)"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "semver",
"value": "[6.6.142,6.7.0)"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "semver",
"value": "[6.12.92,6.13.0)"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "semver",
"value": "[6.18.34,6.19.0)"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "semver",
"value": "[7.0.11,7.1.0)"
}
},
{
"platform": null,
"status": "unaffected",
"versions": {
"scheme": "generic",
"value": "[7.1,*]"
}
}
],
"enrichment": {
"confidence": 99.0,
"confidence_source": "inferred",
"scores": [
{
"score": 99.0,
"source": "inferred"
},
{
"score": 100.0,
"source": "matching"
}
]
},
"original": {
"product": "Linux",
"source": "cna",
"vendor": "Linux"
},
"product": "linux_kernel",
"vendor": "linux"
}
],
"created": "2026-07-22T04:15:12.202791+00:00",
"updated": "2026-08-13T18:15:04.812762+00:00",
"vendors": [
"linux",
"linux$PRODUCT$linux_kernel"
]
},
"epss": {
"score": 0.00162
},
"mitre": {
"cpes": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"created": "2026-07-19T15:41:01.534000+00:00",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nphonet/pep: disable BH around forwarded sk_receive_skb()\n\nThe networking receive path is usually run from softirq context, but\nprotocols that take the socket lock may have packets stored in the\nbacklog and processed later from process context. In that case\nrelease_sock() -> __release_sock() drops the slock with spin_unlock_bh()\nand then calls sk->sk_backlog_rcv() with bottom halves enabled.\n\nTypical sk_backlog_rcv handlers process the socket whose backlog is\nbeing drained, so the BH state at entry is irrelevant for the slocks\nthey touch. pep_do_rcv() is different: when the inbound skb targets an\nexisting PEP pipe, it forwards the skb to a different *child* socket\nvia sk_receive_skb(). That helper takes the child slock with\nbh_lock_sock_nested(), which is just spin_lock_nested() and assumes BH\nis already off. The same child slock therefore ends up acquired with\nBH on (process path) and with BH off (softirq path):\n\n process context softirq context\n --------------- ---------------\n release_sock(listener) __netif_receive_skb()\n __release_sock() phonet_rcv()\n spin_unlock_bh() __sk_receive_skb(listener)\n [BH now ENABLED] [BH already disabled]\n sk_backlog_rcv: sk_backlog_rcv:\n pep_do_rcv() pep_do_rcv()\n sk_receive_skb(child) sk_receive_skb(child)\n bh_lock_sock_nested(child) bh_lock_sock_nested(child)\n => SOFTIRQ-ON-W => IN-SOFTIRQ-W\n\nLockdep flags this as inconsistent lock state, and it can become a real\nself-deadlock if a softirq on the same CPU tries to receive to the same\nchild socket while its slock is held in the BH-enabled path:\n\n WARNING: inconsistent lock state\n inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.\n (slock-AF_PHONET/1){+.?.}-{3:3}, at: __sk_receive_skb+0x1cf/0x900\n __sk_receive_skb net/core/sock.c:563\n sk_receive_skb include/net/sock.h:2022 [inline]\n pep_do_rcv net/phonet/pep.c:675\n sk_backlog_rcv include/net/sock.h:1190\n __release_sock net/core/sock.c:3216\n release_sock net/core/sock.c:3815\n pep_sock_accept net/phonet/pep.c:879\n\nWrap the forwarded sk_receive_skb() in local_bh_disable() /\nlocal_bh_enable() so the child slock is always acquired with BH off.\nlocal_bh_disable() nests safely on the softirq path.\n\nDiscovered via in-house syzkaller fuzzing; the same root cause also\non the linux-6.1.y syzbot dashboard as extid 44f0626dd6284f02663c.\nReproduced under KASAN + LOCKDEP + PROVE_LOCKING, reproducer:\nhttps://pastebin.com/A3t8xzCR",
"metrics": {
"cvssV2_0": {},
"cvssV3_0": {},
"cvssV3_1": {},
"cvssV4_0": {}
},
"mitre_repo_path": "cves/2026/64xxx/CVE-2026-64177.json",
"references": [
"https://git.kernel.org/stable/c/02c04df84de709060f63e1d52ec67488c4f6f212",
"https://git.kernel.org/stable/c/8420aa4900417797323dd567ba9d1512280c2dc3",
"https://git.kernel.org/stable/c/84bc87beb4cd77670939b446326788e4c9b3db37",
"https://git.kernel.org/stable/c/a3fc8f2dacd1c37325977fc1fbbf3d52141df99e",
"https://git.kernel.org/stable/c/b2606c302d7f2b4ee48da05e32ed60aed1b0cd53",
"https://git.kernel.org/stable/c/bd795f106b3889fb0706c6e4831c4b27e2b5666b",
"https://git.kernel.org/stable/c/dbc81608e3a653dea6cf403f20cae35468b8ab9c",
"https://git.kernel.org/stable/c/f08c45076e4fd8b0adbc5eb186d6e6a3e7350d7b"
],
"title": "phonet/pep: disable BH around forwarded sk_receive_skb()",
"updated": "2026-07-19T15:41:01.534000+00:00",
"vendors": [
"linux",
"linux$PRODUCT$linux_kernel"
],
"weaknesses": []
},
"nvd": {
"cpes": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*"
],
"created": "2026-07-19T16:17:59.977000+00:00",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nphonet/pep: disable BH around forwarded sk_receive_skb()\n\nThe networking receive path is usually run from softirq context, but\nprotocols that take the socket lock may have packets stored in the\nbacklog and processed later from process context. In that case\nrelease_sock() -> __release_sock() drops the slock with spin_unlock_bh()\nand then calls sk->sk_backlog_rcv() with bottom halves enabled.\n\nTypical sk_backlog_rcv handlers process the socket whose backlog is\nbeing drained, so the BH state at entry is irrelevant for the slocks\nthey touch. pep_do_rcv() is different: when the inbound skb targets an\nexisting PEP pipe, it forwards the skb to a different *child* socket\nvia sk_receive_skb(). That helper takes the child slock with\nbh_lock_sock_nested(), which is just spin_lock_nested() and assumes BH\nis already off. The same child slock therefore ends up acquired with\nBH on (process path) and with BH off (softirq path):\n\n process context softirq context\n --------------- ---------------\n release_sock(listener) __netif_receive_skb()\n __release_sock() phonet_rcv()\n spin_unlock_bh() __sk_receive_skb(listener)\n [BH now ENABLED] [BH already disabled]\n sk_backlog_rcv: sk_backlog_rcv:\n pep_do_rcv() pep_do_rcv()\n sk_receive_skb(child) sk_receive_skb(child)\n bh_lock_sock_nested(child) bh_lock_sock_nested(child)\n => SOFTIRQ-ON-W => IN-SOFTIRQ-W\n\nLockdep flags this as inconsistent lock state, and it can become a real\nself-deadlock if a softirq on the same CPU tries to receive to the same\nchild socket while its slock is held in the BH-enabled path:\n\n WARNING: inconsistent lock state\n inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.\n (slock-AF_PHONET/1){+.?.}-{3:3}, at: __sk_receive_skb+0x1cf/0x900\n __sk_receive_skb net/core/sock.c:563\n sk_receive_skb include/net/sock.h:2022 [inline]\n pep_do_rcv net/phonet/pep.c:675\n sk_backlog_rcv include/net/sock.h:1190\n __release_sock net/core/sock.c:3216\n release_sock net/core/sock.c:3815\n pep_sock_accept net/phonet/pep.c:879\n\nWrap the forwarded sk_receive_skb() in local_bh_disable() /\nlocal_bh_enable() so the child slock is always acquired with BH off.\nlocal_bh_disable() nests safely on the softirq path.\n\nDiscovered via in-house syzkaller fuzzing; the same root cause also\non the linux-6.1.y syzbot dashboard as extid 44f0626dd6284f02663c.\nReproduced under KASAN + LOCKDEP + PROVE_LOCKING, reproducer:\nhttps://pastebin.com/A3t8xzCR",
"metrics": {
"cvssV2_0": {},
"cvssV3_0": {},
"cvssV3_1": {
"score": 5.5,
"vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
},
"cvssV4_0": {}
},
"nvd_repo_path": "2026/CVE-2026-64177.json",
"references": [
"https://git.kernel.org/stable/c/02c04df84de709060f63e1d52ec67488c4f6f212",
"https://git.kernel.org/stable/c/8420aa4900417797323dd567ba9d1512280c2dc3",
"https://git.kernel.org/stable/c/84bc87beb4cd77670939b446326788e4c9b3db37",
"https://git.kernel.org/stable/c/a3fc8f2dacd1c37325977fc1fbbf3d52141df99e",
"https://git.kernel.org/stable/c/b2606c302d7f2b4ee48da05e32ed60aed1b0cd53",
"https://git.kernel.org/stable/c/bd795f106b3889fb0706c6e4831c4b27e2b5666b",
"https://git.kernel.org/stable/c/dbc81608e3a653dea6cf403f20cae35468b8ab9c",
"https://git.kernel.org/stable/c/f08c45076e4fd8b0adbc5eb186d6e6a3e7350d7b"
],
"title": null,
"updated": "2026-08-13T15:32:45.440000+00:00",
"vendors": [
"linux",
"linux$PRODUCT$linux_kernel"
],
"weaknesses": [
"NVD-CWE-noinfo"
]
},
"opencve": {
"changes": [
{
"created": "2026-07-19T16:15:00+00:00",
"data": [
{
"details": {
"new": "In the Linux kernel, the following vulnerability has been resolved:\n\nphonet/pep: disable BH around forwarded sk_receive_skb()\n\nThe networking receive path is usually run from softirq context, but\nprotocols that take the socket lock may have packets stored in the\nbacklog and processed later from process context. In that case\nrelease_sock() -> __release_sock() drops the slock with spin_unlock_bh()\nand then calls sk->sk_backlog_rcv() with bottom halves enabled.\n\nTypical sk_backlog_rcv handlers process the socket whose backlog is\nbeing drained, so the BH state at entry is irrelevant for the slocks\nthey touch. pep_do_rcv() is different: when the inbound skb targets an\nexisting PEP pipe, it forwards the skb to a different *child* socket\nvia sk_receive_skb(). That helper takes the child slock with\nbh_lock_sock_nested(), which is just spin_lock_nested() and assumes BH\nis already off. The same child slock therefore ends up acquired with\nBH on (process path) and with BH off (softirq path):\n\n process context softirq context\n --------------- ---------------\n release_sock(listener) __netif_receive_skb()\n __release_sock() phonet_rcv()\n spin_unlock_bh() __sk_receive_skb(listener)\n [BH now ENABLED] [BH already disabled]\n sk_backlog_rcv: sk_backlog_rcv:\n pep_do_rcv() pep_do_rcv()\n sk_receive_skb(child) sk_receive_skb(child)\n bh_lock_sock_nested(child) bh_lock_sock_nested(child)\n => SOFTIRQ-ON-W => IN-SOFTIRQ-W\n\nLockdep flags this as inconsistent lock state, and it can become a real\nself-deadlock if a softirq on the same CPU tries to receive to the same\nchild socket while its slock is held in the BH-enabled path:\n\n WARNING: inconsistent lock state\n inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.\n (slock-AF_PHONET/1){+.?.}-{3:3}, at: __sk_receive_skb+0x1cf/0x900\n __sk_receive_skb net/core/sock.c:563\n sk_receive_skb include/net/sock.h:2022 [inline]\n pep_do_rcv net/phonet/pep.c:675\n sk_backlog_rcv include/net/sock.h:1190\n __release_sock net/core/sock.c:3216\n release_sock net/core/sock.c:3815\n pep_sock_accept net/phonet/pep.c:879\n\nWrap the forwarded sk_receive_skb() in local_bh_disable() /\nlocal_bh_enable() so the child slock is always acquired with BH off.\nlocal_bh_disable() nests safely on the softirq path.\n\nDiscovered via in-house syzkaller fuzzing; the same root cause also\non the linux-6.1.y syzbot dashboard as extid 44f0626dd6284f02663c.\nReproduced under KASAN + LOCKDEP + PROVE_LOCKING, reproducer:\nhttps://pastebin.com/A3t8xzCR",
"old": null
},
"type": "description"
},
{
"details": {
"new": "phonet/pep: disable BH around forwarded sk_receive_skb()",
"old": null
},
"type": "title"
},
{
"details": [
"linux",
"linux$PRODUCT$linux_kernel"
],
"type": "first_time"
},
{
"details": {
"added": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"removed": []
},
"type": "cpes"
},
{
"details": {
"added": [
"linux",
"linux$PRODUCT$linux_kernel"
],
"removed": []
},
"type": "vendors"
},
{
"details": {
"added": [
"https://git.kernel.org/stable/c/02c04df84de709060f63e1d52ec67488c4f6f212",
"https://git.kernel.org/stable/c/8420aa4900417797323dd567ba9d1512280c2dc3",
"https://git.kernel.org/stable/c/84bc87beb4cd77670939b446326788e4c9b3db37",
"https://git.kernel.org/stable/c/a3fc8f2dacd1c37325977fc1fbbf3d52141df99e",
"https://git.kernel.org/stable/c/b2606c302d7f2b4ee48da05e32ed60aed1b0cd53",
"https://git.kernel.org/stable/c/bd795f106b3889fb0706c6e4831c4b27e2b5666b",
"https://git.kernel.org/stable/c/dbc81608e3a653dea6cf403f20cae35468b8ab9c",
"https://git.kernel.org/stable/c/f08c45076e4fd8b0adbc5eb186d6e6a3e7350d7b"
],
"removed": []
},
"type": "references"
}
],
"id": "deb8a7e1-0d4d-41dd-9611-07a5f4773c96"
},
{
"created": "2026-07-21T12:15:00+00:00",
"data": [
{
"details": {
"added": [
"CWE-833"
],
"removed": []
},
"type": "weaknesses"
},
{
"details": {
"added": [
"https://lore.kernel.org/linux-cve-announce/2026071937-CVE-2026-64177-79cf@gregkh/T",
"https://nvd.nist.gov/vuln/detail/CVE-2026-64177",
"https://www.cve.org/CVERecord?id=CVE-2026-64177"
],
"removed": []
},
"type": "references"
},
{
"details": {
"added": {
"cvssV3_1": {
"score": 5.5,
"vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
},
"removed": {},
"updated": {
"threat_severity": {
"new": "Moderate",
"old": null
}
}
},
"type": "metrics"
}
],
"id": "c01e66ff-f44f-4081-87e5-05210a643737"
},
{
"created": "2026-08-13T15:45:00+00:00",
"data": [
{
"details": {
"added": [
"NVD-CWE-noinfo"
],
"removed": []
},
"type": "weaknesses"
},
{
"details": {
"added": [
"cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*"
],
"removed": []
},
"type": "cpes"
}
],
"id": "4d823a0b-540c-4d38-888b-55df6e772d12"
}
],
"cpes": {
"data": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*"
],
"providers": [
"mitre",
"nvd"
]
},
"created": {
"data": "2026-07-19T00:00:00+00:00",
"provider": "redhat"
},
"description": {
"data": "In the Linux kernel, the following vulnerability has been resolved:\n\nphonet/pep: disable BH around forwarded sk_receive_skb()\n\nThe networking receive path is usually run from softirq context, but\nprotocols that take the socket lock may have packets stored in the\nbacklog and processed later from process context. In that case\nrelease_sock() -> __release_sock() drops the slock with spin_unlock_bh()\nand then calls sk->sk_backlog_rcv() with bottom halves enabled.\n\nTypical sk_backlog_rcv handlers process the socket whose backlog is\nbeing drained, so the BH state at entry is irrelevant for the slocks\nthey touch. pep_do_rcv() is different: when the inbound skb targets an\nexisting PEP pipe, it forwards the skb to a different *child* socket\nvia sk_receive_skb(). That helper takes the child slock with\nbh_lock_sock_nested(), which is just spin_lock_nested() and assumes BH\nis already off. The same child slock therefore ends up acquired with\nBH on (process path) and with BH off (softirq path):\n\n process context softirq context\n --------------- ---------------\n release_sock(listener) __netif_receive_skb()\n __release_sock() phonet_rcv()\n spin_unlock_bh() __sk_receive_skb(listener)\n [BH now ENABLED] [BH already disabled]\n sk_backlog_rcv: sk_backlog_rcv:\n pep_do_rcv() pep_do_rcv()\n sk_receive_skb(child) sk_receive_skb(child)\n bh_lock_sock_nested(child) bh_lock_sock_nested(child)\n => SOFTIRQ-ON-W => IN-SOFTIRQ-W\n\nLockdep flags this as inconsistent lock state, and it can become a real\nself-deadlock if a softirq on the same CPU tries to receive to the same\nchild socket while its slock is held in the BH-enabled path:\n\n WARNING: inconsistent lock state\n inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.\n (slock-AF_PHONET/1){+.?.}-{3:3}, at: __sk_receive_skb+0x1cf/0x900\n __sk_receive_skb net/core/sock.c:563\n sk_receive_skb include/net/sock.h:2022 [inline]\n pep_do_rcv net/phonet/pep.c:675\n sk_backlog_rcv include/net/sock.h:1190\n __release_sock net/core/sock.c:3216\n release_sock net/core/sock.c:3815\n pep_sock_accept net/phonet/pep.c:879\n\nWrap the forwarded sk_receive_skb() in local_bh_disable() /\nlocal_bh_enable() so the child slock is always acquired with BH off.\nlocal_bh_disable() nests safely on the softirq path.\n\nDiscovered via in-house syzkaller fuzzing; the same root cause also\non the linux-6.1.y syzbot dashboard as extid 44f0626dd6284f02663c.\nReproduced under KASAN + LOCKDEP + PROVE_LOCKING, reproducer:\nhttps://pastebin.com/A3t8xzCR",
"provider": "mitre"
},
"metrics": {
"cvssV2_0": {
"data": {},
"provider": null
},
"cvssV3_0": {
"data": {},
"provider": null
},
"cvssV3_1": {
"data": {
"score": 5.5,
"vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
},
"provider": "nvd"
},
"cvssV4_0": {
"data": {},
"provider": null
},
"epss": {
"data": {
"score": 0.00162
},
"provider": "first"
},
"kev": {
"data": {},
"provider": null
},
"ssvc": {
"data": {},
"provider": null
},
"threat_severity": {
"data": "Moderate",
"provider": "redhat"
}
},
"references": {
"data": [
"https://git.kernel.org/stable/c/02c04df84de709060f63e1d52ec67488c4f6f212",
"https://git.kernel.org/stable/c/8420aa4900417797323dd567ba9d1512280c2dc3",
"https://git.kernel.org/stable/c/84bc87beb4cd77670939b446326788e4c9b3db37",
"https://git.kernel.org/stable/c/a3fc8f2dacd1c37325977fc1fbbf3d52141df99e",
"https://git.kernel.org/stable/c/b2606c302d7f2b4ee48da05e32ed60aed1b0cd53",
"https://git.kernel.org/stable/c/bd795f106b3889fb0706c6e4831c4b27e2b5666b",
"https://git.kernel.org/stable/c/dbc81608e3a653dea6cf403f20cae35468b8ab9c",
"https://git.kernel.org/stable/c/f08c45076e4fd8b0adbc5eb186d6e6a3e7350d7b",
"https://lore.kernel.org/linux-cve-announce/2026071937-CVE-2026-64177-79cf@gregkh/T",
"https://nvd.nist.gov/vuln/detail/CVE-2026-64177",
"https://www.cve.org/CVERecord?id=CVE-2026-64177"
],
"providers": [
"mitre",
"nvd",
"redhat"
]
},
"title": {
"data": "phonet/pep: disable BH around forwarded sk_receive_skb()",
"provider": "mitre"
},
"updated": {
"data": "2026-08-13T15:32:45.440000+00:00",
"provider": "nvd"
},
"vendors": {
"data": [
"linux",
"linux$PRODUCT$linux_kernel"
],
"providers": [
"mitre",
"nvd",
"enrichment"
]
},
"weaknesses": {
"data": [
"CWE-833",
"NVD-CWE-noinfo"
],
"providers": [
"nvd",
"redhat"
]
}
},
"redhat": {
"cpes": [],
"created": "2026-07-19T00:00:00+00:00",
"description": "In the Linux kernel, the following vulnerability has been resolved:\nphonet/pep: disable BH around forwarded sk_receive_skb()\nThe networking receive path is usually run from softirq context, but\nprotocols that take the socket lock may have packets stored in the\nbacklog and processed later from process context. In that case\nrelease_sock() -> __release_sock() drops the slock with spin_unlock_bh()\nand then calls sk->sk_backlog_rcv() with bottom halves enabled.\nTypical sk_backlog_rcv handlers process the socket whose backlog is\nbeing drained, so the BH state at entry is irrelevant for the slocks\nthey touch. pep_do_rcv() is different: when the inbound skb targets an\nexisting PEP pipe, it forwards the skb to a different *child* socket\nvia sk_receive_skb(). That helper takes the child slock with\nbh_lock_sock_nested(), which is just spin_lock_nested() and assumes BH\nis already off. The same child slock therefore ends up acquired with\nBH on (process path) and with BH off (softirq path):\nprocess context softirq context\n--------------- ---------------\nrelease_sock(listener) __netif_receive_skb()\n__release_sock() phonet_rcv()\nspin_unlock_bh() __sk_receive_skb(listener)\n[BH now ENABLED] [BH already disabled]\nsk_backlog_rcv: sk_backlog_rcv:\npep_do_rcv() pep_do_rcv()\nsk_receive_skb(child) sk_receive_skb(child)\nbh_lock_sock_nested(child) bh_lock_sock_nested(child)\n=> SOFTIRQ-ON-W => IN-SOFTIRQ-W\nLockdep flags this as inconsistent lock state, and it can become a real\nself-deadlock if a softirq on the same CPU tries to receive to the same\nchild socket while its slock is held in the BH-enabled path:\nWARNING: inconsistent lock state\ninconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.\n(slock-AF_PHONET/1){+.?.}-{3:3}, at: __sk_receive_skb+0x1cf/0x900\n__sk_receive_skb net/core/sock.c:563\nsk_receive_skb include/net/sock.h:2022 [inline]\npep_do_rcv net/phonet/pep.c:675\nsk_backlog_rcv include/net/sock.h:1190\n__release_sock net/core/sock.c:3216\nrelease_sock net/core/sock.c:3815\npep_sock_accept net/phonet/pep.c:879\nWrap the forwarded sk_receive_skb() in local_bh_disable() /\nlocal_bh_enable() so the child slock is always acquired with BH off.\nlocal_bh_disable() nests safely on the softirq path.\nDiscovered via in-house syzkaller fuzzing; the same root cause also\non the linux-6.1.y syzbot dashboard as extid 44f0626dd6284f02663c.\nReproduced under KASAN + LOCKDEP + PROVE_LOCKING, reproducer:\nhttps://pastebin.com/A3t8xzCR",
"metrics": {
"cvssV2_0": {},
"cvssV3_0": {},
"cvssV3_1": {
"score": 5.5,
"vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
},
"threat_severity": "Moderate"
},
"redhat_repo_path": "2026/CVE-2026-64177.json",
"references": [
"https://lore.kernel.org/linux-cve-announce/2026071937-CVE-2026-64177-79cf@gregkh/T",
"https://nvd.nist.gov/vuln/detail/CVE-2026-64177",
"https://www.cve.org/CVERecord?id=CVE-2026-64177"
],
"title": "kernel: phonet/pep: disable BH around forwarded sk_receive_skb()",
"updated": "2026-07-19T00:00:00+00:00",
"vendors": [],
"weaknesses": [
"CWE-833"
]
}
}
Enrichment data
Aggregated bundle (all enrichments)