CVE-2023-53144

Published: February 5, 2025
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.
Unknown
CVSS v2:

Status

DocFilters Release Package State Justification Comment
22.3 lzma (17.01) Needs Triage
22.2 lzma (17.01) Needs Triage
22.1 lzma (17.01) Needs Triage
21.11.1 lzma (17.01) Needs Triage
21.11 lzma (17.01) Needs Triage
21.8.1 lzma (17.01) Needs Triage
21.8 lzma (17.01) Needs Triage
21.5.1 lzma (17.01) Needs Triage
21.5.0 lzma (17.01) Needs Triage
21.2.0 lzma (17.01) Needs Triage
11.4.20 lzma (17.01) Needs Triage
11.4.19.3667 lzma (17.01) Needs Triage
11.4.18.3599 lzma (17.01) Needs Triage
11.4.17 lzma (17.01) Needs Triage
11.4.16.3445 lzma (17.01) Needs Triage
11.4.15.3368 lzma (17.01) Needs Triage
11.4.14.3263 lzma (17.01) Needs Triage
11.4.13.3179 lzma (17.01) Needs Triage
11.4.12.3054 lzma (17.01) Needs Triage
11.4.11.3040 lzma (17.01) Needs Triage
11.4.11.2990 lzma (17.01) Needs Triage
11.4.10.2934 lzma (17.01) Needs Triage
11.4.9.2878 lzma (17.01) Needs Triage
11.4.8.2822 lzma (17.01) Needs Triage

Severity score breakdown

References