From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F1CF81F4283 for ; Fri, 27 Dec 2024 13:56:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735307778; cv=none; b=QVkbpWtquBhOuSS41zy6Q7u4Jji12Mc6hboOWl4n5+pT9SyEGEE94Xd6F/tuZl/N3rTDw0NWLwAdZ9oPrgyAWmrn5iM5MdsfGhvgaFt8KxUxogghKKuFZLSNEyxCUxK6gxlZKyWJUfhTRr7DfZjaOL5TYfs30SnPO5Wnowe73/0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735307778; c=relaxed/simple; bh=gN8XbH9/aR8WVUoZ4/lHQc83oTRv6rz+G2YrCP2SHoY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=FPDEnkWfgtSXAtKqNhwhrU9i1KI9qiSPgu5R2GCnxIQE7/XRQP88eCLSLKJfy5OqSjM960uO8pDfsFGskJUBwyBAz1zzkZIKNGh8usl9QXAe/mdQ/HPFJDTt4Fha6kOw9sn9pHwOih8ksCeabD/lsCMyL4qAw/bRhcUSxW4UPlg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=KJ4jOOUa; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="KJ4jOOUa" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5A621C4CED0; Fri, 27 Dec 2024 13:56:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1735307777; bh=gN8XbH9/aR8WVUoZ4/lHQc83oTRv6rz+G2YrCP2SHoY=; h=From:To:Cc:Subject:Date:Reply-to:From; b=KJ4jOOUaeCMRghrQxoB41Xg02E9Nqrwmm7uJbyf4hLBkaOyiDO5IGTYvESGfappEV 4x0k+7ZsUuEZe2N2J2NNSoxbODpR1JWE5oNW6AtFNrRddskxoPDVcP3YR6nMDeQdrp 12ysUd2j2oQfHngZkN3wctt+idku1UgdZy+6QzJE= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2024-53233: unicode: Fix utf8_load() error path Date: Fri, 27 Dec 2024 14:53:19 +0100 Message-ID: <2024122737-CVE-2024-53233-ab02@gregkh> X-Mailer: git-send-email 2.47.1 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3287; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=gN8XbH9/aR8WVUoZ4/lHQc83oTRv6rz+G2YrCP2SHoY=; b=owGbwMvMwCRo6H6F97bub03G02pJDOl5G9X63Rv/b5W9v23unNTIhbdi3WLtFu7lihL3++F94 OqDO/uudMSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBElLsZFszo74laWTK/JDGX xVtZ5Urr7SB1G4YFJ0OdM/yzchy+Gke++FU/4/mPo/oXAQ== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: unicode: Fix utf8_load() error path utf8_load() requests the symbol "utf8_data_table" and then checks if the requested UTF-8 version is supported. If it's unsupported, it tries to put the data table using symbol_put(). If an unsupported version is requested, symbol_put() fails like this: kernel BUG at kernel/module/main.c:786! RIP: 0010:__symbol_put+0x93/0xb0 Call Trace: ? __die_body.cold+0x19/0x27 ? die+0x2e/0x50 ? do_trap+0xca/0x110 ? do_error_trap+0x65/0x80 ? __symbol_put+0x93/0xb0 ? exc_invalid_op+0x51/0x70 ? __symbol_put+0x93/0xb0 ? asm_exc_invalid_op+0x1a/0x20 ? __pfx_cmp_name+0x10/0x10 ? __symbol_put+0x93/0xb0 ? __symbol_put+0x62/0xb0 utf8_load+0xf8/0x150 That happens because symbol_put() expects the unique string that identify the symbol, instead of a pointer to the loaded symbol. Fix that by using such string. The Linux kernel CVE team has assigned CVE-2024-53233 to this issue. Affected and fixed versions =========================== Issue introduced in 5.17 with commit 2b3d047870120bcd46d7cc257d19ff49328fd585 and fixed in 6.1.120 with commit 4387cef540f36c2c9297460758cc2438305a24a0 Issue introduced in 5.17 with commit 2b3d047870120bcd46d7cc257d19ff49328fd585 and fixed in 6.6.64 with commit c4b6c1781f6cc4e2283120ac8d873864b8056f21 Issue introduced in 5.17 with commit 2b3d047870120bcd46d7cc257d19ff49328fd585 and fixed in 6.11.11 with commit 6504dd27123966dc455494cb55217c04ca479121 Issue introduced in 5.17 with commit 2b3d047870120bcd46d7cc257d19ff49328fd585 and fixed in 6.12.2 with commit 89933f8ab3b4cad5ac14ea56a39947d1ffe7d0e3 Issue introduced in 5.17 with commit 2b3d047870120bcd46d7cc257d19ff49328fd585 and fixed in 6.13-rc1 with commit 156bb2c569cd869583c593d27a5bd69e7b2a4264 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-2024-53233 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: fs/unicode/utf8-core.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/4387cef540f36c2c9297460758cc2438305a24a0 https://git.kernel.org/stable/c/c4b6c1781f6cc4e2283120ac8d873864b8056f21 https://git.kernel.org/stable/c/6504dd27123966dc455494cb55217c04ca479121 https://git.kernel.org/stable/c/89933f8ab3b4cad5ac14ea56a39947d1ffe7d0e3 https://git.kernel.org/stable/c/156bb2c569cd869583c593d27a5bd69e7b2a4264