Answer in brief
CVE-2022-49664 records a High severity (CVSS 7.5) vulnerability in tipc: move bc link creation back to tipc_node_create. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 <456bc338871c4a52117dd5ef29cce3745456d248 || >=4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 <35fcb2ba35b4d9b592b558c3bcc6e0d90e213588 || >=4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 <e52910e671f58c619e33dac476b11b35e2d3ab6f || >=4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 <cb8092d70a6f5f01ec1490fce4d35efed3ed996c || 0b8f0026bbd4df1688e1726026476e60762daf2a || >=5.4.287 <5.5 | 456bc338871c4a52117dd5ef29cce3745456d248, 35fcb2ba35b4d9b592b558c3bcc6e0d90e213588, e52910e671f58c619e33dac476b11b35e2d3ab6f, cb8092d70a6f5f01ec1490fce4d35efed3ed996c, 5.5 |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49664 records a High severity (CVSS 7.5) vulnerability in tipc: move bc link creation back to tipc_node_create. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 <456bc338871c4a52117dd5ef29cce3745456d248 || >=4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 <35fcb2ba35b4d9b592b558c3bcc6e0d90e213588 || >=4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 <e52910e671f58c619e33dac476b11b35e2d3ab6f || >=4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 <cb8092d70a6f5f01ec1490fce4d35efed3ed996c || 0b8f0026bbd4df1688e1726026476e60762daf2a || >=5.4.287 <5.5 | 456bc338871c4a52117dd5ef29cce3745456d248, 35fcb2ba35b4d9b592b558c3bcc6e0d90e213588, e52910e671f58c619e33dac476b11b35e2d3ab6f, cb8092d70a6f5f01ec1490fce4d35efed3ed996c, 5.5 |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.