CVE-2026-74281
CVE CVE-2026-74281EUVD EUVD-2026-59428Published 2026-08-15T05:57:51.000ZLast changed 2026-08-17T05:45:22.000ZCVSS 7.5
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.2; patch: 5.15.212; patch: 0; patch: 6.12.97; 37922ea4a3105176357c8d565a9d982c4a08714a <581ef56e5c34d475056ce086dc2ba0e872ba6857; patch: 6.18.40; patch: 6.6.145; 37922ea4a3105176357c8d565a9d982c4a08714a <f683200b83a0085d4e11abea8c1fdd9fdfb95b0b; 37922ea4a3105176357c8d565a9d982c4a08714a <cd1955f81bd8ebeef51b324989ac871ad1947fb6; 4.17; 37922ea4a3105176357c8d565a9d982c4a08714a <f1715d92ee3095d9215b493a8603a81f646fcf61; 37922ea4a3105176357c8d565a9d982c4a08714a <973bf0ed896b9898668dbadb82ed849d7d573010; patch: 6.1.178; 37922ea4a3105176357c8d565a9d982c4a08714a <7e401233f9bb74a626e70698d0d62f3a94ac0676; 37922ea4a3105176357c8d565a9d982c4a08714a <2afb648f7b99216c687db1f89739c995e1144153; patch: 7.1.5
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.