LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54194: exfat: use kvmalloc_array/kvfree instead of kmalloc_array/kfree

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can make exFAT removable storage fail to mount on long-running systems with fragmented memory. The described business impact is availability and operational reliability, not data theft or remote compromise. The source does not provide CVSS, CWE, or evidence of active exploitation.

Executive priority

Treat this as a maintenance reliability issue unless exFAT media handling is business-critical. Patch through normal kernel update cycles, with higher priority for kiosks, appliances, or field systems using removable exFAT storage.

Technical view

The exFAT filesystem used kmalloc_array for bitmap allocation, which can require contiguous physical memory. Under fragmentation, allocation can fail during exfat_fill_super when mounting an exFAT block device. The fix changes allocation/freeing to kvmalloc_array and kvfree, allowing non-contiguous backing memory where appropriate.

Likely exposure

Exposure is most relevant to Linux systems that mount exFAT filesystems, especially long-running devices or appliances accepting removable media. The source names Linux as affected but does not provide a clean distro-by-distro matrix.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source states active exploitation. The described scenario is insertion of an exFAT removable device causing mount or recognition failure under memory fragmentation.

Researcher notes

Evidence supports an exFAT mount-time allocation failure fixed by replacing kmalloc_array/kfree with kvmalloc_array/kvfree. The bundle lacks CVSS, CWE, exploit evidence, and precise downstream package status, so distro validation is required.

Mitigation direction

  • Update Linux kernels to versions containing the referenced stable fixes.
  • Check vendor or distribution advisories for backported exFAT fixes.
  • Restrict or disable unneeded exFAT removable-media mounting where operationally acceptable.
  • Prioritize long-running systems that depend on removable exFAT media.

Validation and detection

  • Inventory Linux systems that mount exFAT filesystems or load the exfat module.
  • Compare running kernel packages against vendor advisories and referenced stable commits.
  • Review logs for exFAT mount failures and page allocation failure messages.
  • Confirm patched kernels use the vendor-fixed exFAT allocation path.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54194 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1e49a94cf707204b66a3fb242f2814712c941f52, 1e49a94cf707204b66a3fb242f2814712c941f52, 1e49a94cf707204b66a3fb242f2814712c941f52, 1e49a94cf707204b66a3fb242f2814712c941f52, 1e49a94cf707204b66a3fb242f2814712c941f52unaffected
LinuxLinux5.7, 0, 5.10.190, 5.15.126, 6.1.45, 6.4.10, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.