Homepage

CVE-2026-98098 Affecting kernel-livepatch-6.12.111-136.204 package, versions <1:1.0-0.amzn2023

Severity

 Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.18% (7th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-KERNELLIVEPATCH612111136204-20857409
  • published13 Oct 2026
  • disclosed25 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 25 Sep 2026

NewCVE-2026-98098  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel-livepatch-6.12.111-136.204 to version 1:1.0-0.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3193.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6.12.111-136.204 package and not the kernel-livepatch-6.12.111-136.204 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.