cve/published/2022/CVE-2022-49374.mbox

From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2022-49374: tipc: check attribute length for bearer name

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.

The Linux kernel CVE team has assigned CVE-2022-49374 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.17 with commit cb30a63384bc91d5da06e1cede1115f666a29271 and fixed in 4.19.247 with commit f07670871f4d19e613740eebe210e7e9ea535973
	Issue introduced in 4.17 with commit cb30a63384bc91d5da06e1cede1115f666a29271 and fixed in 5.4.198 with commit 8b91d0dfc839e67708c905648cd0e7507a2263e5
	Issue introduced in 4.17 with commit cb30a63384bc91d5da06e1cede1115f666a29271 and fixed in 5.10.122 with commit b8fac8e321044a9ac50f7185b4e9d91a7745e4b0
	Issue introduced in 4.17 with commit cb30a63384bc91d5da06e1cede1115f666a29271 and fixed in 5.15.47 with commit 92a930fcf4250fe961f6238b99af0bc405799f39
	Issue introduced in 4.17 with commit cb30a63384bc91d5da06e1cede1115f666a29271 and fixed in 5.17.15 with commit 292be63c382ce20673ee61dff1ee9ed4a3dcaae7
	Issue introduced in 4.17 with commit cb30a63384bc91d5da06e1cede1115f666a29271 and fixed in 5.18.4 with commit 3af15272cde28fe5c8489174b8624e232c1775ec
	Issue introduced in 4.17 with commit cb30a63384bc91d5da06e1cede1115f666a29271 and fixed in 5.19 with commit 7f36f798f89bf32c0164049cb0e3fd1af613d0bb

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-49374
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	net/tipc/bearer.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/f07670871f4d19e613740eebe210e7e9ea535973
	https://git.kernel.org/stable/c/8b91d0dfc839e67708c905648cd0e7507a2263e5
	https://git.kernel.org/stable/c/b8fac8e321044a9ac50f7185b4e9d91a7745e4b0
	https://git.kernel.org/stable/c/92a930fcf4250fe961f6238b99af0bc405799f39
	https://git.kernel.org/stable/c/292be63c382ce20673ee61dff1ee9ed4a3dcaae7
	https://git.kernel.org/stable/c/3af15272cde28fe5c8489174b8624e232c1775ec
	https://git.kernel.org/stable/c/7f36f798f89bf32c0164049cb0e3fd1af613d0bb