Vulnerability · Published Dec 30, 2025 · Assigned by Linux
CVE-2023-54194exfat: use kvmalloc_array/kvfree instead of kmalloc_array/kfree
Unrated
In plain English
A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: exfat: use kvmalloc_array/kvfree instead of kmalloc_array/kfree The call stack shown below is a scenario in the Linux 4.19 kernel. Allocating memory failed where exfat fs use kmalloc_array due to system memory fragmentation, while the u-disk was inserted without recognition. Devices such as u-disk using the exfat file system are pluggable and may be insert into the system at any time. However, long-term running systems cannot guarantee the continuity of physical memory. Therefore, it's necessary to address this issue. Binder:2632_6: page allocation failure: order:4, mode:0x6040c0(GFP_KERNEL|__GFP_COMP), nodemask=(null) Call trace: [242178.097582] dump_backtrace+0x0/0x4 [242178.097589] dump_stack+0xf4/0x134 [242178.097598] warn_alloc+0xd8/0x144 [242178.097603] __alloc_pages_nodemask+0x1364/0x1384 [242178.097608] kmalloc_order+0x2c/0x510 [242178.097612] kmalloc_order_trace+0x40/0x16c [242178.097618] __kmalloc+0x360/0x408 [242178.097624] load_alloc_bitmap+0x160/0x284 [242178.097628] exfat_fill_super+0xa3c/0xe7c [242178.097635] mount_bdev+0x2e8/0x3a0 [242178.097638] exfat_fs_mount+0x40/0x50 [242178.097643] mount_fs+0x138/0x2e8 [242178.097649] vfs_kern_mount+0x90/0x270 [242178.097655] do_mount+0x798/0x173c [242178.097659] ksys_mount+0x114/0x1ac [242178.097665] __arm64_sys_mount+0x24/0x34 [242178.097671] el0_svc_common+0xb8/0x1b8 [242178.097676] el0_svc_handler+0x74/0x90 [242178.097681] el0_svc+0x8/0x340 By analyzing the exfat code,we found that continuous physical memory is not required here,so kvmalloc_array is used can solve this problem.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.52-1 | DEBIAN-CVE-2023-54194 |
| Debian:13 | linux | 6.4.11-1 | DEBIAN-CVE-2023-54194 |
| Debian:14 | linux | 6.4.11-1 | DEBIAN-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux | 5.15.0-88.98 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1049.54 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1051.59 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1051.59.1 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1046.54 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1046.51 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1032.38 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1042.45 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1045.51 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1046.51 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-88.98 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1040.40 | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1019.19 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1006.6 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1047.53 | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1042.45 | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-54194 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-54194 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1e49a94cf707204b66a3fb242f2814712c941f52 – before 79d16a84ea41272dfcb0c00f9798ddd0edd8098d1e49a94cf707204b66a3fb242f2814712c941f52 – before 8a34a242cf03211cc89f68308d149b793f63c4791e49a94cf707204b66a3fb242f2814712c941f52 – before 1427a7e96fb90d0896f74f5bcd21feb03cc7c3d01e49a94cf707204b66a3fb242f2814712c941f52 – before 0c5c3e8a2550b6b2a304b45f260296db9c09df961e49a94cf707204b66a3fb242f2814712c941f52 – before daf60d6cca26e50d65dac374db92e58de745ad26 |
| Linux | Linux | 5.7 |
References
- https://git.kernel.org/stable/c/79d16a84ea41272dfcb0c00f9798ddd0edd8098d
- https://git.kernel.org/stable/c/8a34a242cf03211cc89f68308d149b793f63c479
- https://git.kernel.org/stable/c/1427a7e96fb90d0896f74f5bcd21feb03cc7c3d0
- https://git.kernel.org/stable/c/0c5c3e8a2550b6b2a304b45f260296db9c09df96
- https://git.kernel.org/stable/c/daf60d6cca26e50d65dac374db92e58de745ad26