CVE-2026-53292 json
net: phonet: do not BUG_ON() in pn_socket_autobind() on failed bind
published 2026-06-26 4 mo ago modified 2026-10-30 9 d ago also EUVD-2026-39897
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: phonet: do not BUG_ON() in pn_socket_autobind() on failed bind
syzbot reported a kernel BUG triggered from pn_socket_sendmsg() via pn_socket_autobind():
kernel BUG at net/phonet/socket.c:213! RIP: 0010:pn_socket_autobind net/phonet/socket.c:213 [inline] RIP: 0010:pn_socket_sendmsg+0x240/0x250 net/phonet/socket.c:421 Call Trace: sock_sendmsg_nosec+0x112/0x150 net/socket.c:797 __sock_sendmsg net/socket.c:812 [inline] __sys_sendto+0x402/0x590 net/socket.c:2280 ...
pn_socket_autobind() calls pn_socket_bind() with port 0 and, on -EINVAL, assumes the socket was already bound and asserts that the port is non-zero:
err = pn_socket_bind(sock, ..., sizeof(struct sockaddr_pn)); if (err != -EINVAL) return err; BUG_ON(!pn_port(pn_sk(sock->sk)->sobject)); return 0; /* socket was already bound */
However pn_socket_bind() also returns -EINVAL when sk->sk_state is not TCP_CLOSE, even when the socket has never been bound and pn_port() is still 0. In that case the BUG_ON() fires and panics the kernel from a user-triggerable path.
Treat the "bind returned -EINVAL but pn_port() is still 0" case as a regular error and propagate -EINVAL to the caller instead of crashing. Existing callers already translate a non-zero return from pn_socket_autobind() into -ENOBUFS/-EAGAIN, so returning -EINVAL here only changes behaviour from panic to a normal errno.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.57, 7.0.10, 7.1
- linux Debian 13 6.12.115-2
- linux Debian 14 7.0.10-1
debian advisories DEBIAN-CVE-2026-53292
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gke Ubuntu 26.04 LTS 7.0.0-1003.4
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1010.10
- linux-azure Ubuntu 26.04 LTS 7.0.0-1010.10
- linux-raspi Ubuntu 26.04 LTS 7.0.0-1015.15
- linux-riscv Ubuntu 26.04 LTS 7.0.0-28.28.1
ubuntu advisories UBUNTU-CVE-2026-53292
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/6972021488e3142f30a89d8035eebeefbbe65656 commit
- git.kernel.org/stable/c/4255c8f756b78d07800baf3320bdbdc130c54193 commit
- git.kernel.org/stable/c/363c7fcac553dc2aa12fc90c6e5e6eba87500269 commit
- git.kernel.org/stable/c/5459933a799aaf642cbeb35fdf7e78c59bf2fb9b commit
- git.kernel.org/stable/c/6db58ee730bf434d1afca91b91826e26688856ed commit
- git.kernel.org/stable/c/5b0c911bcdbd982f7748d11c0b39ec5808eae2de commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-53292 updated cvss 5.5
kernel: net: phonet: do not BUG_ON() in pn_socket_autobind() on failed bind
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-617 Reachable Assertion
- Technology feeds
References
- git.kernel.org /stable/c/6972021488e3142f30a89d8035eebeefbbe65656
- git.kernel.org /stable/c/4255c8f756b78d07800baf3320bdbdc130c54193
- git.kernel.org /stable/c/363c7fcac553dc2aa12fc90c6e5e6eba87500269
- git.kernel.org /stable/c/5459933a799aaf642cbeb35fdf7e78c59bf2fb9b
-
git.kernel.org
/stable/c/6db58ee730bf434d1afca91b91826e26688856ed
patch
-
git.kernel.org
/stable/c/5b0c911bcdbd982f7748d11c0b39ec5808eae2de
patch
Sources
- CVE List CVE-2026-53292
- NVD CVE-2026-53292
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.