cbcvebase.
CVE-2026-63808
published 2026-07-19

CVE-2026-63808: In the Linux kernel, the following vulnerability has been resolved: exfat: fix potential use-after-free in exfat_find_dir_entry() In exfat_find_dir_entry()…

PriorityP349critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.50%
40.1th percentile
In the Linux kernel, the following vulnerability has been resolved: exfat: fix potential use-after-free in exfat_find_dir_entry() 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 fc961522ddbd ("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.

Affected

10 ranges
VendorProductVersion rangeFixed in
linuxlinux——
linuxlinux>= ca06197382bde0a3bc20215595d1c9ce20c6e341 < e6f1a11cfb808441a43ffae9b476cc135732cd27e6f1a11cfb808441a43ffae9b476cc135732cd27
linuxlinux>= ca06197382bde0a3bc20215595d1c9ce20c6e341 < e48f413c2815787b8cade2795e194e3c4cd782efe48f413c2815787b8cade2795e194e3c4cd782ef
linuxlinux>= ca06197382bde0a3bc20215595d1c9ce20c6e341 < 06c4e1e9967d332ac33ba38b7819851089ff935906c4e1e9967d332ac33ba38b7819851089ff9359
linuxlinux>= ca06197382bde0a3bc20215595d1c9ce20c6e341 < 8e0abc17fbd7e305802e84fe98b4950d50f9c4338e0abc17fbd7e305802e84fe98b4950d50f9c433
linuxlinux>= ca06197382bde0a3bc20215595d1c9ce20c6e341 < 4d101016d5e587f820b3ae2d5bb6770d863426494d101016d5e587f820b3ae2d5bb6770d86342649
linuxlinux>= ca06197382bde0a3bc20215595d1c9ce20c6e341 < adfacfbaeae2cb760f492357cc36b41f84ef7f86adfacfbaeae2cb760f492357cc36b41f84ef7f86
linuxlinux>= ca06197382bde0a3bc20215595d1c9ce20c6e341 < 708b97e792945d3e4653939fd3405d71a61ad065708b97e792945d3e4653939fd3405d71a61ad065
linuxlinux>= ca06197382bde0a3bc20215595d1c9ce20c6e341 < 3f5f8ee9917cc2b9076ac533492d8a200edcabb83f5f8ee9917cc2b9076ac533492d8a200edcabb8
linuxlinux_kernel——

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.8CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.