CVE-2022-49374

tipc: check attribute length for bearer name

MEDIUM

5.5

CVSS Score

Published: February 26, 2025 at 02:11 AM UTC

Updated: June 17, 2026 at 05:17 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: check attribute length for bearer name syzbot reported uninit-value: ===================================================== BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:644 [inline] BUG: KMSAN: uninit-value in string+0x4f9/0x6f0 lib/vsprintf.c:725 string_nocheck lib/vsprintf.c:644 [inline] string+0x4f9/0x6f0 lib/vsprintf.c:725 vsnprintf+0x2222/0x3650 lib/vsprintf.c:2806 vprintk_store+0x537/0x2150 kernel/printk/printk.c:2158 vprintk_emit+0x28b/0xab0 kernel/printk/printk.c:2256 vprintk_default+0x86/0xa0 kernel/printk/printk.c:2283 vprintk+0x15f/0x180 kernel/printk/printk_safe.c:50 _printk+0x18d/0x1cf kernel/printk/printk.c:2293 tipc_enable_bearer net/tipc/bearer.c:371 [inline] __tipc_nl_bearer_enable+0x2022/0x22a0 net/tipc/bearer.c:1033 tipc_nl_bearer_enable+0x6c/0xb0 net/tipc/bearer.c:1042 genl_family_rcv_msg_doit net/netlink/genetlink.c:731 [inline] - Do sanity check the attribute length for TIPC_NLA_BEARER_NAME. - Do not use 'illegal name' in printing message.

Affected

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

Linux Kernel · Linux

95%

4.17 ≤ v < 4.19.2474.17 ≤ v < 5.10.1224.17 ≤ v < 5.15.474.17 ≤ v < 5.17.154.17 ≤ v < 5.18.44.17 ≤ v < 5.194.17 ≤ v < 5.4.1984.20 ≤ v < 5.4.1985.11 ≤ v < 5.15.475.16 ≤ v < 5.17.155.18 ≤ v < 5.18.45.5 ≤ v < 5.10.1224.17cb30a63384bc91d5da06e1cede1115f666a29271

Vendor states this is fixed in 292be63c382ce20673ee61dff1ee9ed4a3dcaae7 (fixed)

Vendor states this is fixed in 3af15272cde28fe5c8489174b8624e232c1775ec (fixed)

Vendor states this is fixed in 7f36f798f89bf32c0164049cb0e3fd1af613d0bb (fixed)

Vendor states this is fixed in 8b91d0dfc839e67708c905648cd0e7507a2263e5 (fixed)

Vendor states this is fixed in 92a930fcf4250fe961f6238b99af0bc405799f39 (fixed)

Vendor states this is fixed in b8fac8e321044a9ac50f7185b4e9d91a7745e4b0 (fixed)

Vendor states this is fixed in f07670871f4d19e613740eebe210e7e9ea535973 (fixed)

Vendor states this is fixed in 4.17 (unaffected)

Vendor states this is fixed in 4.19.247 (unaffected)

Vendor states this is fixed in 5.10.122 (unaffected)

Vendor states this is fixed in 5.15.47 (unaffected)

Vendor states this is fixed in 5.17.15 (unaffected)

Vendor states this is fixed in 5.18.4 (unaffected)

Vendor states this is fixed in 5.19 (unaffected)

Vendor states this is fixed in 5.4.198 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references