CVE-2026-64296

CVE CVE-2026-64296EUVD EUVD-2026-49008Published 2026-07-25T08:49:33.000ZLast changed 2026-08-05T12:40:40.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux ca06197382bde0a3bc20215595d1c9ce20c6e341 <3a1230e7b043c62737b05a3e9275ca83a43ad20a; patch: 6.12.96; 5.7; ca06197382bde0a3bc20215595d1c9ce20c6e341 <72a2589d82eb001c94b74bcfe6f9a599bd9bef60; patch: 7.1.4; patch: 6.1.178; ca06197382bde0a3bc20215595d1c9ce20c6e341 <fae76a94b35ee8c0e2eb6f64caca01d75c6d34e4; ca06197382bde0a3bc20215595d1c9ce20c6e341 <33c0b96d7e1672be1de0053786637ea46fb81507; ca06197382bde0a3bc20215595d1c9ce20c6e341 <c8e041c68c0bbb73aa62371ee63947bb6949d8b2; patch: 6.6.145; patch: 7.2-rc1; patch: 5.15.212; patch: 6.18.39; ca06197382bde0a3bc20215595d1c9ce20c6e341 <727bf7783a2936ffd55c628dddfd69343e511dcf; ca06197382bde0a3bc20215595d1c9ce20c6e341 <cf85180b8a015029ee147694eaf4e0b3537e9432; ca06197382bde0a3bc20215595d1c9ce20c6e341 <ce4736c1e6c4cfbf1ac409a8c328a0b69546c9a0; patch: 0; patch: 5.10.261

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.