exfat: fix handling of damaged volume in exfat_create_upcase_table()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s exFAT module can loop indefinitely when an exFAT volume’s upcase table size is zero, such as on corrupted media or a misbehaving device. This occurs when the module processes the damaged volume; the input does not establish an attacker access path or authentication requirements.
Engineers running Linux systems that process exFAT volumes should check their kernel versions; affected versions are not specified.