| From bippy-1.1.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2022-49862: tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header |
| |
| This is a follow-up for commit 974cb0e3e7c9 ("tipc: fix uninit-value |
| in tipc_nl_compat_name_table_dump") where it should have type casted |
| sizeof(..) to int to work when TLV_GET_DATA_LEN() returns a negative |
| value. |
| |
| syzbot reported a call trace because of it: |
| |
| BUG: KMSAN: uninit-value in ... |
| tipc_nl_compat_name_table_dump+0x841/0xea0 net/tipc/netlink_compat.c:934 |
| __tipc_nl_compat_dumpit+0xab2/0x1320 net/tipc/netlink_compat.c:238 |
| tipc_nl_compat_dumpit+0x991/0xb50 net/tipc/netlink_compat.c:321 |
| tipc_nl_compat_recv+0xb6e/0x1640 net/tipc/netlink_compat.c:1324 |
| genl_family_rcv_msg_doit net/netlink/genetlink.c:731 [inline] |
| genl_family_rcv_msg net/netlink/genetlink.c:775 [inline] |
| genl_rcv_msg+0x103f/0x1260 net/netlink/genetlink.c:792 |
| netlink_rcv_skb+0x3a5/0x6c0 net/netlink/af_netlink.c:2501 |
| genl_rcv+0x3c/0x50 net/netlink/genetlink.c:803 |
| netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] |
| netlink_unicast+0xf3b/0x1270 net/netlink/af_netlink.c:1345 |
| netlink_sendmsg+0x1288/0x1440 net/netlink/af_netlink.c:1921 |
| sock_sendmsg_nosec net/socket.c:714 [inline] |
| sock_sendmsg net/socket.c:734 [inline] |
| |
| The Linux kernel CVE team has assigned CVE-2022-49862 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.9.152 with commit 4c559fb7e111077b56f62ccf833a52d8169cde19 and fixed in 4.9.334 with commit 082707d3df191bf5bb8801d43e4ce3dea39ca173 |
| Issue introduced in 4.14.95 with commit 2aae1723dea1235ffef183daf0694805297424f6 and fixed in 4.14.300 with commit a0ead1d648df9c456baec832b494513ef405949a |
| Issue introduced in 4.19.17 with commit 2d5fc1d492d194aa2986c5a9d8a48a60e9143a72 and fixed in 4.19.267 with commit 55a253a6753a603e80b95932ca971ba514aa6ce7 |
| Issue introduced in 5.0 with commit 974cb0e3e7c963ced06c4e32c5b2884173fa5e01 and fixed in 5.4.225 with commit 36769b9477491a7af6635863bd950309c1e1b96c |
| Issue introduced in 5.0 with commit 974cb0e3e7c963ced06c4e32c5b2884173fa5e01 and fixed in 5.10.155 with commit f31dd158580940938f77514b87337a777520185a |
| Issue introduced in 5.0 with commit 974cb0e3e7c963ced06c4e32c5b2884173fa5e01 and fixed in 5.15.79 with commit 301caa06091af4d5cf056ac8249cbda4e6029c6a |
| Issue introduced in 5.0 with commit 974cb0e3e7c963ced06c4e32c5b2884173fa5e01 and fixed in 6.0.9 with commit 6cee2c60bd168279852ac7dbe54c2b70d1028644 |
| Issue introduced in 5.0 with commit 974cb0e3e7c963ced06c4e32c5b2884173fa5e01 and fixed in 6.1 with commit 1c075b192fe41030457cd4a5f7dea730412bca40 |
| Issue introduced in 4.4.172 with commit c25352f9ad5dffb4de95069e67891e2aa2e99e50 |
| Issue introduced in 4.20.4 with commit 5486e8d46560ca2b4d86cbd7d3a66d9913b2ac65 |
| |
| 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-49862 |
| 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/netlink_compat.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/082707d3df191bf5bb8801d43e4ce3dea39ca173 |
| https://git.kernel.org/stable/c/a0ead1d648df9c456baec832b494513ef405949a |
| https://git.kernel.org/stable/c/55a253a6753a603e80b95932ca971ba514aa6ce7 |
| https://git.kernel.org/stable/c/36769b9477491a7af6635863bd950309c1e1b96c |
| https://git.kernel.org/stable/c/f31dd158580940938f77514b87337a777520185a |
| https://git.kernel.org/stable/c/301caa06091af4d5cf056ac8249cbda4e6029c6a |
| https://git.kernel.org/stable/c/6cee2c60bd168279852ac7dbe54c2b70d1028644 |
| https://git.kernel.org/stable/c/1c075b192fe41030457cd4a5f7dea730412bca40 |
