linux-cve-announce - CVE-2023-53144: erofs: fix wrong kunmap when using LZMA on HIGHMEM platforms

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2025050239-CVE-2023-53144-2ad8@gregkh>
Date: Fri,  2 May 2025 17:56:49 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53144: erofs: fix wrong kunmap when using LZMA on HIGHMEM platforms

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

erofs: fix wrong kunmap when using LZMA on HIGHMEM platforms

As the call trace shown, the root cause is kunmap incorrect pages:

 BUG: kernel NULL pointer dereference, address: 00000000
 CPU: 1 PID: 40 Comm: kworker/u5:0 Not tainted 6.2.0-rc5 #4
 Workqueue: erofs_worker z_erofs_decompressqueue_work
 EIP: z_erofs_lzma_decompress+0x34b/0x8ac
  z_erofs_decompress+0x12/0x14
  z_erofs_decompress_queue+0x7e7/0xb1c
  z_erofs_decompressqueue_work+0x32/0x60
  process_one_work+0x24b/0x4d8
  ? process_one_work+0x1a4/0x4d8
  worker_thread+0x14c/0x3fc
  kthread+0xe6/0x10c
  ? rescuer_thread+0x358/0x358
  ? kthread_complete_and_exit+0x18/0x18
  ret_from_fork+0x1c/0x28
 ---[ end trace 0000000000000000 ]---

The bug is trivial and should be fixed now.  It has no impact on
!HIGHMEM platforms.

The Linux kernel CVE team has assigned CVE-2023-53144 to this issue.


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

	Issue introduced in 5.16 with commit 622ceaddb7649ca328832f50ba1400af778d75fa and fixed in 6.1.20 with commit fa4056781ac067b5946c6811459e1a36842047fd
	Issue introduced in 5.16 with commit 622ceaddb7649ca328832f50ba1400af778d75fa and fixed in 6.2.7 with commit 28aea8ae6cf212a5bf3ed962b27921e2029ad754
	Issue introduced in 5.16 with commit 622ceaddb7649ca328832f50ba1400af778d75fa and fixed in 6.3 with commit 8f121dfb15f7b4ab345992ce96003eb63fd608f4

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-2023-53144
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/erofs/decompressor_lzma.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/fa4056781ac067b5946c6811459e1a36842047fd
	https://git.kernel.org/stable/c/28aea8ae6cf212a5bf3ed962b27921e2029ad754
	https://git.kernel.org/stable/c/8f121dfb15f7b4ab345992ce96003eb63fd608f4