CVE-2026-98098: tipc: fix NULL deref in tipc_named_node_up() on empty publication list
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 246a4b4aace490664927042e93400a6f940d197f, 6188cf0c989dea60f2efe800eaebb7d0bd16e2b2, 68619f965329d2f7b113a3d5811aa23198f39105; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 246a4b4aace490664927042e93400a6f940d197f, 6188cf0c989dea60f2efe800eaebb7d0bd16e2b2, 68619f965329d2f7b113a3d5811aa23198f39105; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 25, 2026
- Updated
- Oct 28, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.15 and later · before 5.15.222
- linux linux kernel5.16 and later · before 6.1.189
- linux linux kernel6.2 and later · before 6.6.158
- linux linux kernel6.7 and later · before 6.12.111
- linux linux kernel6.13 and later · up to 6.18.53 inclusive
- linux linux kernel6.19 and later · before 7.2.7
- linux linux kernel7.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.15affected
- a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 and later · before 246a4b4aace490664927042e93400a6f940d197faffected · git
- a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 and later · before 6188cf0c989dea60f2efe800eaebb7d0bd16e2b2affected · git
- a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 and later · before b5344e459996afb45e30fdc407b41e6674793b21affected · git
- a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 and later · before 68619f965329d2f7b113a3d5811aa23198f39105affected · git
- a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 and later · before ad805326d874062f8bc72a94884f86046148cde3affected · git
- a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 and later · before d0d82f1214f321143c5dbc2e48e4a4e6c4226895affected · git
- a5e7ac5ce134d8f72f59631011fafa7bbf7ca174 and later · before b3b76e9f4f2476f1135b2ba7743a821db4a0df4baffected · git
- before 3.15not affected · semver
- 5.15.222 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-98096Sep 25, 2026 · ipv6: sr: restore network header before routing and forwarding29Monitor
- ← EarlierCVE-2026-98097Sep 25, 2026 · tipc: Dont send random pad bytes in RESET/ACTIVATE messages21Monitor
- Later →CVE-2026-98099Sep 25, 2026 · ipv6: mcast: use rcu_assign_pointer() for __rcu list updates18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 246a4b4aace490664927042e93400a6f940d197f | Vendor (CNA) |
| Linux Linux | 6188cf0c989dea60f2efe800eaebb7d0bd16e2b2 | Vendor (CNA) |
| Linux Linux | 68619f965329d2f7b113a3d5811aa23198f39105 | Vendor (CNA) |
| Linux Linux | ad805326d874062f8bc72a94884f86046148cde3 | Vendor (CNA) |
| Linux Linux | b3b76e9f4f2476f1135b2ba7743a821db4a0df4b | Vendor (CNA) |
| Linux Linux | b5344e459996afb45e30fdc407b41e6674793b21 | Vendor (CNA) |
| Linux Linux | d0d82f1214f321143c5dbc2e48e4a4e6c4226895 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- CVSS— → 5.5
- Severity— → medium
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/6188cf0c989dea60f2efe800eaebb7d0bd16e2b2
- git.kernel.org/stable/c/68619f965329d2f7b113a3d5811aa23198f39105
- git.kernel.org/stable/c/ad805326d874062f8bc72a94884f86046148cde3
- git.kernel.org/stable/c/b3b76e9f4f2476f1135b2ba7743a821db4a0df4b
- git.kernel.org/stable/c/b5344e459996afb45e30fdc407b41e6674793b21
- git.kernel.org/stable/c/d0d82f1214f321143c5dbc2e48e4a4e6c4226895
Vendor advisories and official records. Exploit/PoC links are deliberately left out.