tipc: fix NULL deref in tipc_named_node_up() on empty publication list
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: tipc: fix NULL deref in tipc_named_node_up() on empty publication list User-space applications can bind a large number of service addresses to one or more sockets. Each binding of a local-scope service address inserts one entry (publication) into the TIPC name table. If the number of these publications exceeds TIPC_MAX_PUBL (65535), protocol service types (such as node state and link state) are no longer inserted into the name table. This causes two issues: 1. User-space applications subscribing to node or link up/down events stop receiving notifications. 2. A NULL pointer dereference can occur: BUG: kernel NULL pointer dereference, address: 00000000000000d0 ... CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc4-default+ #5 PREEMPT(full) ... RIP: 0010:tipc_named_node_up (./include/linux/skbuff.h:2251 net/tipc/name_distr.c:195 net/tipc/name_distr.c:221) ... Call Trace: <IRQ> tipc_node_write_unlock (net/tipc/node.c:428) tipc_rcv (net/tipc/node.c:934 net/tipc/node.c:2189) tipc_udp_recv (net/tipc/udp_media.c:389) Thread 1 (tipc_net_finalize) | Thread 2 (named_distribute) -----------------------------|----------------------------- | ... | list_for_each_entry(publ, pls, binding_node) { | ... | __skb_queue_tail(list, skb); | ... | } | ... | hdr = buf_msg(skb_peek_tail(list)); ... | tipc_nametbl_publish(); | If 'tipc_nametbl_publish()' (Thread 1) fails because the number of local publications reaches TIPC_MAX_PUBL, list (Thread 2) will be empty. As a result, NULL is passed to 'buf_msg()', leading to a NULL pointer dereference. Fix these issues by allowing protocol service types (node state, link state, and topology server) to be inserted into the name table unconditionally. This ensures that users subscribing to these types always receive notifications. In addition, the maximum number of local user publications is reduced to (TIPC_MAX_PUBL - 1). This ensures that the maximum bulk size calculated in tipc_link_set_queue_limits() remains valid.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 · fixed in 246a4b4aace490664927042e93400a6f940d197f; From a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 · fixed in 6188cf0c989dea60f2efe800eaebb7d0bd16e2b2; From a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 · fixed in b5344e459996afb45e30fdc407b41e6674793b21; From a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 · fixed in 68619f965329d2f7b113a3d5811aa23198f39105; From a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 · fixed in ad805326d874062f8bc72a94884f86046148cde3; From a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 · fixed in d0d82f1214f321143c5dbc2e48e4a4e6c4226895; From a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 · fixed in b3b76e9f4f2476f1135b2ba7743a821db4a0df4b
- Linux Linux
3.15
- KernelLinux
From 3.15.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7
References 7
git.kernel.org
- stable/c/246a4b4aace490664927042e93400a6f940d197f
- stable/c/6188cf0c989dea60f2efe800eaebb7d0bd16e2b2
- stable/c/b5344e459996afb45e30fdc407b41e6674793b21
- stable/c/68619f965329d2f7b113a3d5811aa23198f39105
- stable/c/ad805326d874062f8bc72a94884f86046148cde3
- stable/c/d0d82f1214f321143c5dbc2e48e4a4e6c4226895
- stable/c/b3b76e9f4f2476f1135b2ba7743a821db4a0df4b