exfat: fix handling of damaged volume in exfat_create_upcase_table() (CVE-2026-93828) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93828

exfat: fix handling of damaged volume in exfat_create_upcase_table()

Answer in brief

CVE-2026-93828 records a Unknown severity vulnerability in exfat: fix handling of damaged volume in exfat_create_upcase_table(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <60ace93811609e4dd883e9de5fb4462ed834160a \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2cc0b612343638057ef321ce735201a7c2f52f25 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <20dd3185d13865214ff25b0bf7b931e8d73be1ac \|\| >=0 <6.12.111 \|\| >=0 <6.18.53	60ace93811609e4dd883e9de5fb4462ed834160a, 2cc0b612343638057ef321ce735201a7c2f52f25, 20dd3185d13865214ff25b0bf7b931e8d73be1ac, 6.12.111, 6.18.53

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux.
Review the reported fix. Update Linux/Linux to 60ace93811609e4dd883e9de5fb4462ed834160a if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.