VulnerabilityPublished 26 Jun 2026Updated 21 Oct 2026

CVE-2026-53292: Linux kernel · net: phonet: do not BUG_ON() in pn_socket_autobind() on failed bind

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in 5459933a799aaf642cbeb35fdf7e78c59bf2fb9b : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:30 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5459933a799aaf642cbeb35fdf7e78c59bf2fb9b, 4255c8f756b78d07800baf3320bdbdc130c54193, 363c7fcac553dc2aa12fc90c6e5e6eba87500269 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ba113a94b7503ee23ffe819e7045134b0c1d31de, < 5459933a799aaf642cbeb35fdf7e78c59bf2fb9b	Fixed in 5459933a799aaf642cbeb35fdf7e78c59bf2fb9b
LinuxLinux	Affected ≥ ba113a94b7503ee23ffe819e7045134b0c1d31de, < 4255c8f756b78d07800baf3320bdbdc130c54193	Fixed in 4255c8f756b78d07800baf3320bdbdc130c54193
LinuxLinux	Affected ≥ ba113a94b7503ee23ffe819e7045134b0c1d31de, < 363c7fcac553dc2aa12fc90c6e5e6eba87500269	Fixed in 363c7fcac553dc2aa12fc90c6e5e6eba87500269
LinuxLinux	Affected ≥ ba113a94b7503ee23ffe819e7045134b0c1d31de, < 6db58ee730bf434d1afca91b91826e26688856ed	Fixed in 6db58ee730bf434d1afca91b91826e26688856ed
LinuxLinux	Affected ≥ ba113a94b7503ee23ffe819e7045134b0c1d31de, < 5b0c911bcdbd982f7748d11c0b39ec5808eae2de	Fixed in 5b0c911bcdbd982f7748d11c0b39ec5808eae2de
LinuxLinux	Affected =2.6.28	Fixed in–

Description

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.

References

Community reviews

Loading reviews…