{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-98098 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98098 is a medium-severity vulnerability in Linux kernel, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98098 and fix it if it is affected.\n\nWhat it is: CVE-2026-98098 is a medium-severity vulnerability in Linux kernel, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98098 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98098/ (Markdown: https://insights.sbomify.com/CVE-2026-98098/index.md)","id":"CVE-2026-98098","markdown":"https://insights.sbomify.com/CVE-2026-98098/index.md","name":"CVE-2026-98098","record":{"aliases":["AZL-104502","BELL-CVE-2026-98098","DEBIAN-CVE-2026-98098","GHSA-vgfp-jj93-v4hf","UBUNTU-CVE-2026-98098"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel TIPC","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel NULL pointer dereference in the TIPC module by exhausting the publication list, causing a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntipc: fix NULL deref in tipc_named_node_up() on empty publication list\n\nUser-space applications can bind a large number of service addresses to\none or more sockets. Each binding of a local-scope service address inserts\none entry (publication) into the TIPC name table. If the number of these\npublications exceeds TIPC_MAX_PUBL (65535), protocol service types\n(such as node state and link state) are no longer inserted into the name\ntable. This causes two issues:\n\n1. User-space applications subscribing to node or link up/down events\n   stop receiving notifications.\n\n2. A NULL pointer dereference can occur:\n\n   BUG: kernel NULL pointer dereference, address: 00000000000000d0\n   ...\n   CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc4-default+ #5 PREEMPT(full)\n   ...\n   RIP: 0010:tipc_named_node_up (./include/linux/skbuff.h:2251 net/tipc/name_distr.c:195 net/tipc/name_distr.c:221)\n   ...\n   Call Trace:\n   \u003cIRQ\u003e\n   tipc_node_write_unlock (net/tipc/node.c:428)\n   tipc_rcv (net/tipc/node.c:934 net/tipc/node.c:2189)\n   tipc_udp_recv (net/tipc/udp_media.c:389)\n\n   Thread 1 (tipc_net_finalize) | Thread 2 (named_distribute)\n   -----------------------------|-----------------------------\n                                | ...\n                                | list_for_each_entry(publ, pls, binding_node) {\n                                | ...\n                                | __skb_queue_tail(list, skb);\n                                | ...\n                                | }\n                                | ...\n                                | hdr = buf_msg(skb_peek_tail(list));\n   ...                          |\n   tipc_nametbl_publish();      |\n\n   If 'tipc_nametbl_publish()' (Thread 1) fails because the number of\n   local publications reaches TIPC_MAX_PUBL, list (Thread 2) will be empty. As a\n   result, NULL is passed to 'buf_msg()', leading to a NULL pointer dereference.\n\nFix these issues by allowing protocol service types (node state, link state,\nand topology server) to be inserted into the name table unconditionally.\nThis ensures that users subscribing to these types always receive\nnotifications. In addition, the maximum number of local user publications is\nreduced to (TIPC_MAX_PUBL - 1). This ensures that the maximum bulk size\ncalculated in tipc_link_set_queue_limits() remains valid.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"tipc: fix NULL deref in tipc_named_node_up() on empty publication list","id":"CVE-2026-98098","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"ipv6: mcast: use rcu_assign_pointer() for __rcu list updates","id":"CVE-2026-98099"},"packages":[],"prev":{"headline":"tipc: Dont send random pad bytes in RESET/ACTIVATE messages","id":"CVE-2026-98097"},"products":["Linux"],"published":"2026-09-25","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel NULL pointer dereference in the TIPC module by exhausting the publication list, causing a system crash.","url":"https://insights.sbomify.com/CVE-2026-98098/"}