CVE-2022-49664

tipc: move bc link creation back to tipc_node_create

MEDIUM
5.5
CVSS Score
Published: February 26, 2025 at 02:23 AM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: move bc link creation back to tipc_node_create Shuang Li reported a NULL pointer dereference crash: [] BUG: kernel NULL pointer dereference, address: 0000000000000068 [] RIP: 0010:tipc_link_is_up+0x5/0x10 [tipc] [] Call Trace: [] <IRQ> [] tipc_bcast_rcv+0xa2/0x190 [tipc] [] tipc_node_bc_rcv+0x8b/0x200 [tipc] [] tipc_rcv+0x3af/0x5b0 [tipc] [] tipc_udp_recv+0xc7/0x1e0 [tipc] It was caused by the 'l' passed into tipc_bcast_rcv() is NULL. When it creates a node in tipc_node_check_dest(), after inserting the new node into hashtable in tipc_node_create(), it creates the bc link. However, there is a gap between this insert and bc link creation, a bc packet may come in and get the node from the hashtable then try to dereference its bc link, which is NULL. This patch is to fix it by moving the bc link creation before inserting into the hashtable. Note that for a preliminary node becoming "real", the bc link creation should also be called before it's rehashed, as we don't create it for preliminary nodes.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.4.2875.11 ≤ v < 5.15.535.16 ≤ v < 5.18.105.4.287 ≤ v < 5.10.1295.4.287 ≤ v < 5.55.5 ≤ v < 5.10.1295.5 ≤ v < 5.15.535.5 ≤ v < 5.18.105.5 ≤ v < 5.190b8f0026bbd4df1688e1726026476e60762daf2a4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f45.19 rc15.19 rc25.19 rc35.19 rc45.4.287
Vendor states this is fixed in 35fcb2ba35b4d9b592b558c3bcc6e0d90e213588 (fixed)
Vendor states this is fixed in 456bc338871c4a52117dd5ef29cce3745456d248 (fixed)
Vendor states this is fixed in cb8092d70a6f5f01ec1490fce4d35efed3ed996c (fixed)
Vendor states this is fixed in e52910e671f58c619e33dac476b11b35e2d3ab6f (fixed)
Vendor states this is fixed in 5.10.129 (unaffected)
Vendor states this is fixed in 5.15.53 (unaffected)
Vendor states this is fixed in 5.18.10 (unaffected)
Vendor states this is fixed in 5.19 (unaffected)
Vendor states this is fixed in 5.5 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/35fcb2ba35b4d9b592b558c3bcc6e0d90e213588
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/456bc338871c4a52117dd5ef29cce3745456d248
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cb8092d70a6f5f01ec1490fce4d35efed3ed996c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e52910e671f58c619e33dac476b11b35e2d3ab6f

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card