Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-63808: exfat: fix potential use-after-free in exfat_find_dir_entry()

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.52% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 06c4e1e9967d332ac33ba38b7819851089ff9359, 3f5f8ee9917cc2b9076ac533492d8a200edcabb8, 4d101016d5e587f820b3ae2d5bb6770d86342649.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 06c4e1e9967d332ac33ba38b7819851089ff9359, 3f5f8ee9917cc2b9076ac533492d8a200edcabb8, 4d101016d5e587f820b3ae2d5bb6770d86342649 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Oct 22, 2026
EPSS
0.5% · 44th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-63808

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.7 and later · before 5.10.260
  • linux linux kernel5.11 and later · before 5.15.211
  • linux linux kernel5.16 and later · before 6.1.177
  • linux linux kernel6.2 and later · before 6.6.144
  • linux linux kernel6.7 and later · before 6.12.95
  • linux linux kernel6.13 and later · before 6.18.38
  • linux linux kernel6.19 and later · before 7.1.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.7affected
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before e6f1a11cfb808441a43ffae9b476cc135732cd27affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before e48f413c2815787b8cade2795e194e3c4cd782efaffected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before 06c4e1e9967d332ac33ba38b7819851089ff9359affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before 8e0abc17fbd7e305802e84fe98b4950d50f9c433affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before 4d101016d5e587f820b3ae2d5bb6770d86342649affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before adfacfbaeae2cb760f492357cc36b41f84ef7f86affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before 708b97e792945d3e4653939fd3405d71a61ad065affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before 3f5f8ee9917cc2b9076ac533492d8a200edcabb8affected · git
    • before 5.7not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.51.1.el10_26.12.0-211.51.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-63806Jul 19, 2026 · KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned()
    28Monitor
  • ← EarlierCVE-2026-63807Jul 19, 2026 · KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level
    35Monitor
  • Later →CVE-2026-63809Jul 19, 2026 · bpf: use kvfree() for replaced sysctl write buffer
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux06c4e1e9967d332ac33ba38b7819851089ff9359Vendor (CNA)
Linux Linux3f5f8ee9917cc2b9076ac533492d8a200edcabb8Vendor (CNA)
Linux Linux4d101016d5e587f820b3ae2d5bb6770d86342649Vendor (CNA)
Linux Linux708b97e792945d3e4653939fd3405d71a61ad065Vendor (CNA)
Linux Linux8e0abc17fbd7e305802e84fe98b4950d50f9c433Vendor (CNA)
Linux Linuxadfacfbaeae2cb760f492357cc36b41f84ef7f86Vendor (CNA)
Linux Linuxe48f413c2815787b8cade2795e194e3c4cd782efVendor (CNA)
Linux Linuxe6f1a11cfb808441a43ffae9b476cc135732cd27Vendor (CNA)
almalinux:kernel6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.51.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.177-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.51.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records