linux-cve-announce - CVE-2024-53233: unicode: Fix utf8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2024122737-CVE-2024-53233-ab02@gregkh>
Date: Fri, 27 Dec 2024 14:53:19 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-53233: unicode: Fix utf8_load() error path

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:
  <TASK>
  ? __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