Skip to content
Noroxi
CVE-2026-64296· NVD / CVE Program· CNA Linux

exfat: bound uniname advance in exfat_find_dir_entry()

In the Linux kernel, the following vulnerability has been resolved: exfat: bound uniname advance in exfat_find_dir_entry() In exfat_find_dir_entry(), each TYPE_EXTEND (file name) entry advances the output pointer by a fixed amount while the loop guard only tracks the accumulated name length: if (++order == 2) uniname = p_uniname->name; else uniname += EXFAT_FILE_NAME_LEN; len = exfat_extract_uni_name(ep, entry_uniname); name_len += len; unichar = *(uniname+len); *(uniname+len) = 0x0; uniname grows by EXFAT_FILE_NAME_LEN (15) per name entry, but name_len grows only by the actual extracted length, which is shorter when a name fragment contains an early NUL. The only guard is `name_len >= MAX_NAME_LENGTH`, so a crafted directory with many short name fragments lets uniname run far past the p_uniname->name[MAX_NAME_LENGTH + 3] buffer while name_len stays small, causing an out-of-bounds read and write at *(uniname+len). The sibling extractor exfat_get_uniname_from_ext_entry() already stops on a short fragment (the lockstep `len != EXFAT_FILE_NAME_LEN` guard added in commit d42334578eba ("exfat: check if filename entries exceeds max filename length")); exfat_find_dir_entry() never got the equivalent. Track the per-entry write offset as a count and reject a fragment once the offset, or the offset plus the extracted length, would exceed MAX_NAME_LENGTH, before forming the output pointer.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 6th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CNA vs NVD score

NVD
—
CNA · Linux
7.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.

Affected systems

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.261
  • linux linux kernel5.11 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4

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 72a2589d82eb001c94b74bcfe6f9a599bd9bef60affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before fae76a94b35ee8c0e2eb6f64caca01d75c6d34e4affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before cf85180b8a015029ee147694eaf4e0b3537e9432affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before ce4736c1e6c4cfbf1ac409a8c328a0b69546c9a0affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before 727bf7783a2936ffd55c628dddfd69343e511dcfaffected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before 33c0b96d7e1672be1de0053786637ea46fb81507affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before c8e041c68c0bbb73aa62371ee63947bb6949d8b2affected · git
    • ca06197382bde0a3bc20215595d1c9ce20c6e341 and later · before 3a1230e7b043c62737b05a3e9275ca83a43ad20aaffected · 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
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

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 Linux33c0b96d7e1672be1de0053786637ea46fb81507Vendor (CNA)
Linux Linux3a1230e7b043c62737b05a3e9275ca83a43ad20aVendor (CNA)
Linux Linux727bf7783a2936ffd55c628dddfd69343e511dcfVendor (CNA)
Linux Linux72a2589d82eb001c94b74bcfe6f9a599bd9bef60Vendor (CNA)
Linux Linuxc8e041c68c0bbb73aa62371ee63947bb6949d8b2Vendor (CNA)
Linux Linuxce4736c1e6c4cfbf1ac409a8c328a0b69546c9a0Vendor (CNA)
Linux Linuxcf85180b8a015029ee147694eaf4e0b3537e9432Vendor (CNA)
Linux Linuxfae76a94b35ee8c0e2eb6f64caca01d75c6d34e4Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

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.

Credits

All researchers

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).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • 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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

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.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

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

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records