[CVE-2026-63808][MODERATE 7.0] exfat: fix potential use-after-free in exfat_find_dir_entry()

[CVE-2026-63808][MODERATE 7.0] exfat: fix potential use-after-free in exfat_find_dir_entry()

[AL-KERNEL]

CVE: CVE-2026-63808
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: exfat: fix potential use-after-free in exfat_find_dir_entry()
Commit: e6f1a11cfb808441a43ffae9b476cc135732cd27
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e6f1a11cfb808441a43ffae9b476cc135732cd27
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63808
Analysis date: Sun, 19 Jul 2026 10:28:02 -0400
ActionableScore: 6
ActionableScore lower bound: 5
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A crafted exFAT filesystem can trigger a use-after-release read in `exfat_find_dir_entry()` because directory entry data is accessed through `ep` after `brelse(bh)`, causing at least a local kernel crash risk and requiring manual review for possible stronger UAF impact.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-63808 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63808

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-63808	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;*CWE-672;CWE-825;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A use after free can occur in exfat_find_dir_entry because ep points into bh data and the old code could call brelse(bh) before the TYPE_EXTEND path reads ep in exfat_extract_uni_name. A crafted exFAT image with long file name entries and same hash collisions can force this path and make the kernel read through an expired buffer pointer. For the CVSS the PR:L is used for the paranoid score because a local user may be able to supply or trigger processing of a crafted exFAT filesystem through removable media automount or delegated mount mechanisms, while full administrative control is not always required in desktop or containerized environments. The issue is not network reachable. Impact is at least a local denial of service via kernel crash. In worst case it may allow broader confidentiality or integrity impact because this is a real kernel use after free in filesystem parsing and should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 6)	YES	DANGER DISK UAF KERNEL_PANIC_PLUS_UAF LINUS KPANIC 	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=6
ActionableScoreLower=5

## 1. ActionableScore

* Conservative score: **5**
* Paranoid score: **6**
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* **Local unprivileged trigger: +1**
  A local user may be able to provide or trigger parsing of a crafted exFAT filesystem through removable media automount, desktop storage services, or delegated mount paths. On hardened/server systems this may require mount privileges.

* **Generic memory corruption: +2**
  This is a real stale lifetime bug: `ep` points into `bh->b_data`, but `brelse(bh)` releases the buffer before `ep` is read in the `TYPE_EXTEND` path.

* **Real lifetime corruption: +1**
  The patch fixes use-after-release ordering by moving `brelse(bh)` after the last dereference of `ep`.

* **Availability impact realistic: +1**
  KASAN/DEBUG_PAGEALLOC/PAGE_POISONING confirms a UAF fault with a crafted exFAT image and forced invalidation. An unaided crash on a normal kernel was not reproduced, so this is not scored as a fully reliable crash.

* **Common filesystem/removable-media exposure: +1**
  exFAT is commonly used for removable media and may be enabled as a module on general-purpose distributions.

Negative signals:

* **Hard or unreliable triggering: -1**
  The commit explicitly says ordinary reclaim did not reproduce a crash on an uninstrumented kernel. The deterministic reproducer required debug-only `invalidate_bdev()` instrumentation.

Paranoid-only signal:

* **Weak LPE concern: +1**
  This is a kernel UAF in filesystem parsing, but there is no demonstrated attacker-controlled reclaim, overwrite, callback, type confusion, or refcount takeover. This justifies manual review sensitivity, not a strong LPE assumption.

## 3. Reachability analysis

The bug is reachable when the kernel exFAT driver parses a crafted directory layout with long filename entries and hash-collision behavior that forces the `TYPE_EXTEND` path in `exfat_find_dir_entry()`.

Typical triggering requires one of:

* local ability to mount or cause automount of a crafted exFAT image,
* physical/removable-media access on systems with desktop automount,
* delegated mount capability,
* container/user namespace configurations that expose kernel filesystem mounting.

It is **not network reachable** by itself. On servers where mounting exFAT requires full `CAP_SYS_ADMIN`, practical exposure is lower. On desktops or appliance-style systems that auto-mount removable media, PR:L is more defensible than PR:H.

Call-site confidence: **high**, because the patch shows the exact dereference-after-`brelse()` ordering in the affected function.

## 4. Severity interpretation

This behaves like an **Actionable Moderate** issue with manual review required.

Theoretical risk is higher than a simple crash because this is a confirmed kernel use-after-free style lifetime violation in filesystem parsing. However, realistic exploitation evidence is limited: the demonstrated crash required sanitizer/debug instrumentation and forced invalidation, and the patch does not show a write primitive, controlled reclaim, callback control, or type confusion.

So the conservative interpretation is local DoS / UAF-read risk. The paranoid interpretation keeps it elevated because crafted-filesystem UAF bugs can sometimes become stronger after manual exploitability analysis.

## 5. One-sentence report phrase

A crafted exFAT filesystem can trigger a use-after-release read in `exfat_find_dir_entry()` because directory entry data is accessed through `ep` after `brelse(bh)`, causing at least a local kernel crash risk and requiring manual review for possible stronger UAF impact.

## 6. Manual review recommendation

**MANUAL CHECK REQUIRED**

Reason: confirmed lifetime violation and KASAN UAF in kernel filesystem parsing, local crafted-input reachability, and possible desktop/removable-media exposure. The current evidence does not prove LPE, but the bug class is strong enough that it should not be auto-closed.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: exfat: fix potential use-after-free in exfat_find_dir_entry()
Commit: e6f1a11cfb808441a43ffae9b476cc135732cd27
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e6f1a11cfb808441a43ffae9b476cc135732cd27

Commit description:

In exfat_find_dir_entry(), the buffer_head obtained from
exfat_get_dentry() is released with brelse(bh) before the fall-through
TYPE_EXTEND branch reads the directory entry through ep (which points
into bh->b_data):

	brelse(bh);
	if (entry_type == TYPE_EXTEND) {
		...
		len = exfat_extract_uni_name(ep, entry_uniname);
		...
	}

After brelse() drops our reference, nothing guarantees that the
underlying page backing bh->b_data remains valid for the subsequent
exfat_extract_uni_name() read. This is the same pattern fixed in
commit fc96152 ("exfat: Fix potential use after free in
exfat_load_upcase_table()").

Move brelse(bh) so it runs after ep is no longer dereferenced on
each branch.

Confirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y
+ CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image
(long filename with same-hash collisions forcing the TYPE_EXTEND path).
With a debug-only invalidate_bdev() inserted between brelse(bh) and
the ep read to make the stale-deref window deterministic, the
unpatched kernel faults:

  BUG: KASAN: use-after-free in exfat_find_dir_entry+0x133b/0x15a0
  BUG: unable to handle page fault for address: ffff88801a5fa0c2
  Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI
  RIP: 0010:exfat_find_dir_entry+0x1188/0x15a0

With this patch applied, the same instrumented harness completes
cleanly under the same sanitizer stack. I have not reproduced a
crash on an uninstrumented kernel under ordinary reclaim; the
instrumented A/B establishes the lifetime violation and that the
patch closes it, not an unaided triggerability claim.

Fixes: ca06197 ("exfat: add directory operations")
Cc: stable@vger.kernel.org
Assisted-by: Claude:claude-opus-4-7
Signed-off-by: Michael Bommarito <michael.bommarito@gmail.com>
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  fs/exfat/dir.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e6f1a11cfb808441a43ffae9b476cc135732cd27

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-63808 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63808

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 5
  Paranoid ActionableScore: 6

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).