CVE-2026-74281tipc: reject inverted service ranges from peer bindings
- 7.5HighCVSS base score
- 0.68%Exploitation in 30 daysEPSS · top 47% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.68% · top 47% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected 37922ea4a3105176357c8d565a9d982c4a08714a – < cd1955f81bd8ebeef51b324989ac871ad1947fb6
- affected 37922ea4a3105176357c8d565a9d982c4a08714a – < f683200b83a0085d4e11abea8c1fdd9fdfb95b0b
- affected 37922ea4a3105176357c8d565a9d982c4a08714a – < f1715d92ee3095d9215b493a8603a81f646fcf61
- affected 37922ea4a3105176357c8d565a9d982c4a08714a – < 581ef56e5c34d475056ce086dc2ba0e872ba6857
- affected 37922ea4a3105176357c8d565a9d982c4a08714a – < 7e401233f9bb74a626e70698d0d62f3a94ac0676
- affected 37922ea4a3105176357c8d565a9d982c4a08714a – < 973bf0ed896b9898668dbadb82ed849d7d573010
- affected 37922ea4a3105176357c8d565a9d982c4a08714a – < 2afb648f7b99216c687db1f89739c995e1144153
- affected 4.17
- unaffected < 4.17
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/cd1955f81bd8ebeef51b324989ac871ad1947fb6 (opens in a new tab)
- https://git.kernel.org/stable/c/f683200b83a0085d4e11abea8c1fdd9fdfb95b0b (opens in a new tab)
- https://git.kernel.org/stable/c/f1715d92ee3095d9215b493a8603a81f646fcf61 (opens in a new tab)
- https://git.kernel.org/stable/c/581ef56e5c34d475056ce086dc2ba0e872ba6857 (opens in a new tab)
- https://git.kernel.org/stable/c/7e401233f9bb74a626e70698d0d62f3a94ac0676 (opens in a new tab)
- https://git.kernel.org/stable/c/973bf0ed896b9898668dbadb82ed849d7d573010 (opens in a new tab)
- https://git.kernel.org/stable/c/2afb648f7b99216c687db1f89739c995e1144153 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59428 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74281)Record last updated .