CVE-2026-98098
Undergoing Analysis Undergoing Analysis - In Progress

NULL Pointer Dereference in Linux Kernel TIPC Protocol

Vulnerability report for CVE-2026-98098, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-25

Last updated on: 2026-10-03

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-25
Last Modified
2026-10-03
Generated
2026-10-15
AI Q&A
2026-09-25
EPSS Evaluated
2026-10-14
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux kernel 7.2.0-rc4

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a NULL pointer dereference in the TIPC (Transparent Inter-Process Communication) subsystem. It occurs when user-space applications bind too many service addresses, exceeding the TIPC_MAX_PUBL limit of 65535 publications. This causes protocol service types like node or link state to stop being inserted into the name table, leading to missed notifications for applications subscribing to these events and potential system crashes due to the NULL pointer dereference.

Detection Guidance

Check if TIPC (Transparent Inter-Process Communication) is enabled and monitor for excessive local-scope service address bindings. Commands: lsmod | grep tipc to verify TIPC module, dmesg | grep -i tipc to check for kernel messages, and watch -n 1 'cat /proc/net/tipc/name_table' to observe name table entries.

Impact Analysis

If you use Linux systems with TIPC enabled, this vulnerability could cause applications relying on node or link state notifications to stop receiving updates. In severe cases, it may lead to kernel crashes due to the NULL pointer dereference, resulting in system instability or downtime. Systems with high numbers of service address bindings are most at risk.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it pertains to a kernel-level issue in the TIPC protocol causing NULL pointer dereferences and notification failures. No evidence suggests data breaches or unauthorized access risks that would impact regulatory compliance.

Mitigation Strategies

Reduce the number of local-scope service address bindings to stay below TIPC_MAX_PUBL (65535). Unload the TIPC module if not in use with rmmod tipc. Update the Linux kernel to a patched version where this issue is resolved.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-98098. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart