CVE-2022-49664 [Medium] | Security Vulnerability in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.13%	0.26%	+0.13%
2	2026-04-06	0.03%	0.13%	+0.10%
3	2025-11-21	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.13%

0.26%

+0.13%

2026-04-06

0.03%

0.13%

+0.10%

2025-11-21

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2022-49664

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49664 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-49664
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49664
`suse`	medium	CVE-2022-49664 severity moderate: SUSE including 46 source package names (bpftool-4.18.0-425.3.1.el8, cluster-md-kmp-default, …), 218 product×package rows across 37 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Liberty Linux 8, … (37 product lines)): Known Not Affected 198, Fixed 20.	https://www.suse.com/security/cve/CVE-2022-49664/
`ubuntu`	medium	CVE-2022-49664 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 146, not-affected 123, released 114, needed 22, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49664

Affected software / configurations for CVE-2022-49664

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.4.287, < 5.10.129	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.53	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.18.10	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc1::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc2::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc3::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc4::::::

References for CVE-2022-49664

URL	Tags
https://git.kernel.org/stable/c/35fcb2ba35b4d9b592b558c3bcc6e0d90e213588	Patch
https://git.kernel.org/stable/c/456bc338871c4a52117dd5ef29cce3745456d248	Patch
https://git.kernel.org/stable/c/cb8092d70a6f5f01ec1490fce4d35efed3ed996c	Patch
https://git.kernel.org/stable/c/e52910e671f58c619e33dac476b11b35e2d3ab6f	Patch

URL

CVE-2022-49664 | tipc: move bc link creation back to tipc_node_create

Exploit prediction scoring system (EPSS) score for CVE-2022-49664

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49664

Weakness enumeration for CVE-2022-49664

OS Trackers for CVE-2022-49664

Affected software / configurations for CVE-2022-49664

References for CVE-2022-49664