Skip to main content
VulnerabilityPublished Updated

CVE-2026-98098: Linux kernel · tipc: fix NULL deref in tipc_named_node_up() on empty publication list

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in d0d82f1214f321143c5dbc2e48e4a4e6c4226895 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d0d82f1214f321143c5dbc2e48e4a4e6c4226895, b5344e459996afb45e30fdc407b41e6674793b21, b3b76e9f4f2476f1135b2ba7743a821db4a0df4b +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a5e7ac5ce134d8f72f59631011fafa7bbf7ca174, < d0d82f1214f321143c5dbc2e48e4a4e6c4226895
Fixed in
  • d0d82f1214f321143c5dbc2e48e4a4e6c4226895
LinuxLinuxAffected
  • ≥ a5e7ac5ce134d8f72f59631011fafa7bbf7ca174, < b5344e459996afb45e30fdc407b41e6674793b21
Fixed in
  • b5344e459996afb45e30fdc407b41e6674793b21
LinuxLinuxAffected
  • ≥ a5e7ac5ce134d8f72f59631011fafa7bbf7ca174, < b3b76e9f4f2476f1135b2ba7743a821db4a0df4b
Fixed in
  • b3b76e9f4f2476f1135b2ba7743a821db4a0df4b
LinuxLinuxAffected
  • ≥ a5e7ac5ce134d8f72f59631011fafa7bbf7ca174, < ad805326d874062f8bc72a94884f86046148cde3
Fixed in
  • ad805326d874062f8bc72a94884f86046148cde3
LinuxLinuxAffected
  • ≥ a5e7ac5ce134d8f72f59631011fafa7bbf7ca174, < 68619f965329d2f7b113a3d5811aa23198f39105
Fixed in
  • 68619f965329d2f7b113a3d5811aa23198f39105
LinuxLinuxAffected
  • ≥ a5e7ac5ce134d8f72f59631011fafa7bbf7ca174, < 6188cf0c989dea60f2efe800eaebb7d0bd16e2b2
Fixed in
  • 6188cf0c989dea60f2efe800eaebb7d0bd16e2b2

AI-suggested

A fix is available and has been applied in the Linux kernel commits listed under fixedVersions. Users should update their Linux kernel to a version including these fixes to prevent the NULL pointer dereference and ensure reliable TIPC notifications. No additional mitigation is required beyond applying the official patch.

Description

A vulnerability in the Linux kernel's TIPC subsystem allows a NULL pointer dereference in the function tipc_named_node_up() when the publication list is empty. This occurs if user-space applications bind more than 65535 local-scope service addresses, causing protocol service types to not be inserted into the name table. This results in subscribers not receiving node or link state notifications and triggers a kernel NULL pointer dereference crash. The issue is fixed by ensuring protocol service types are always inserted and reducing the maximum number of local publications by one.

References

Community reviews

Loading reviews…