tipc: reject inverted service ranges from peer bindings
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 37922ea4a3105176357c8d565a9d982c4a08714a · < 973bf0ed896b9898668dbadb82ed849d7d573010| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s TIPC name-distribution path accepts service bindings from peer nodes with inverted range bounds. A peer node can send PUBLICATION items that leak binding-table memory without a per-peer limit. This occurs through peer-node traffic; no user interaction is described.
Engineers running Linux kernels with TIPC should check their exposure; affected versions are not specified.