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

exfat: fix handling of damaged volume in exfat_create_upcase_table()

When the size of the upcase table is set to zero in the dentry for any
reason(e.g. corrupted media or misbehaving device), an integer overflow
causes the module to loop indefinitely.

If the size of the upcase table is read zero, do not attempt to load the
table. Instead, fallback to loading the default upcase table. If the
size of the upcase table is zero or no upcase table is found, raise
exfat_fs_error() to mark the volume read-only.
Published: 2026-09-24
Score: n/a
EPSS: n/a
KEV: No
Impact: Denial of Service via infinite loop on corrupted exfat volumes
Action: Apply Patch
AI Analysis

Impact

An integer overflow in the exfat module’s up‑case table creation causes the kernel to enter an infinite loop whenever the table size is zero, a situation that can arise from corrupted media or misbehaving devices. The loop consumes CPU resources and blocks the kernel context that accessed the filesystem, freezing any processes or threads interacting with that mount until the kernel is rebooted or the volume is remounted. The failure mode is a complete denial of service on the affected system.

Affected Systems

The flaw resides in the Linux kernel’s exfat filesystem driver. Any kernel that ships with the default exfat module is potentially impacted, regardless of version, until the patch that prevents zero‑size table handling is applied.

Risk and Exploitability

No CVSS or EPSS data are available, and the vulnerability is not listed in CISA KEV. The attack vector is likely local, requiring access to a device containing a damaged exfat volume or the ability to cause corruption on a mounted volume. Because the infinite loop occurs in kernel space, exploitation can result in a full system denial of service. The lack of quantified metrics suggests uncertainty in exploitation likelihood, but the nature of the flaw implies a serious availability threat.

Generated by OpenCVE AI on September 25, 2026 at 05:16 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that contains the exfat up‑case table fix (apply the commit or install the latest stable release).
  • Reboot or unload and reload the exfat module so the kernel uses the updated code.
  • If an immediate kernel update is not possible, avoid mounting untrusted exfat volumes or remount any affected volumes as read‑only to limit the impact.

Generated by OpenCVE AI on September 25, 2026 at 05:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 25 Sep 2026 05:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-680

Thu, 24 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: exfat: fix handling of damaged volume in exfat_create_upcase_table() When the size of the upcase table is set to zero in the dentry for any reason(e.g. corrupted media or misbehaving device), an integer overflow causes the module to loop indefinitely. If the size of the upcase table is read zero, do not attempt to load the table. Instead, fallback to loading the default upcase table. If the size of the upcase table is zero or no upcase table is found, raise exfat_fs_error() to mark the volume read-only.
Title exfat: fix handling of damaged volume in exfat_create_upcase_table()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-24T16:03:08.417Z

Reserved: 2026-09-18T17:59:28.793Z

Link: CVE-2026-93828

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T17:17:16.517

Modified: 2026-09-24T17:17:16.517

Link: CVE-2026-93828

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T05:30:18Z

Weaknesses
  • CWE-680

    Integer Overflow to Buffer Overflow