{"api_version":"1","generated_at":"2026-08-22T07:08:11+00:00","cve":"CVE-2026-72209","urls":{"html":"https://cve.report/CVE-2026-72209","api":"https://cve.report/api/cve/CVE-2026-72209.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-72209","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-72209"},"summary":{"title":"ntfs: validate attribute values on lookup","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: validate attribute values on lookup\n\nntfs_attr_find() and ntfs_external_attr_find() check that generic\nresident attribute values fit in their attribute records and that\nfixed-size resident values are large enough. For variable-length resident\nformats, however, the fixed part is not enough: embedded length fields\ncan still point callers past the resident value.\n\nA crafted image can set a small resident $FILE_NAME value_length while\nleaving file_name_length large. Callers then trust file_name_length and\nread past the resident value when converting or comparing the name. This\nwas reproduced with a crafted image under KASAN as a slab-out-of-bounds\nread from the kmalloc-1k MFT record copy. The stack included\nntfs_lookup(), ntfs_iget(), ntfs_read_locked_inode(), ntfs_attr_name_get(),\nntfs_ucstonls(), and utf16s_to_utf8s().\n\nAdd a shared attribute value validator and use it before a lookup path\ncan return an attribute, including the AT_UNUSED enumeration case where\ncallers inspect returned attributes directly. The helper validates\nresident value bounds, minimum resident value sizes, variable-length\n$FILE_NAME fields, and non-resident mapping-pairs metadata that was\npreviously checked separately in both lookup paths.\n\nThis also preserves the intended resident @val matching semantics in the\nexternal attribute lookup path. The old duplicated validation block\noverwrote the actual resident value length with the type-specific minimum\nlength before comparing @val, so variable-length resident values could\nfail to match even when the bytes were identical. Keep the comparison on\nthe actual value length, and make ntfs_attrlist_entry_add() compare\nresident attributes with lowest_vcn zero instead of reading the\nnon-resident union member after a successful resident match.\n\nReject non-resident $FILE_NAME records too: the format requires\n$FILE_NAME to be resident and callers treat returned records as resident.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:21:39","updated_at":"2026-08-17 06:18:21"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"9.8","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"9.8","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":9.8,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/d5803e3345dae9c6470bb61869885236276b9a35","name":"https://git.kernel.org/stable/c/d5803e3345dae9c6470bb61869885236276b9a35","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56","name":"https://git.kernel.org/stable/c/e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-72209","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72209","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6ceb4cc81ef3409ff79dcb959771f9110787397a e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6ceb4cc81ef3409ff79dcb959771f9110787397a d5803e3345dae9c6470bb61869885236276b9a35 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"72209","cve":"CVE-2026-72209","epss":"0.005160000","percentile":"0.415100000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:47"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/ntfs/attrib.c","fs/ntfs/attrlist.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56","status":"affected","version":"6ceb4cc81ef3409ff79dcb959771f9110787397a","versionType":"git"},{"lessThan":"d5803e3345dae9c6470bb61869885236276b9a35","status":"affected","version":"6ceb4cc81ef3409ff79dcb959771f9110787397a","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/ntfs/attrib.c","fs/ntfs/attrlist.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.1"},{"lessThan":"7.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"7.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: validate attribute values on lookup\n\nntfs_attr_find() and ntfs_external_attr_find() check that generic\nresident attribute values fit in their attribute records and that\nfixed-size resident values are large enough. For variable-length resident\nformats, however, the fixed part is not enough: embedded length fields\ncan still point callers past the resident value.\n\nA crafted image can set a small resident $FILE_NAME value_length while\nleaving file_name_length large. Callers then trust file_name_length and\nread past the resident value when converting or comparing the name. This\nwas reproduced with a crafted image under KASAN as a slab-out-of-bounds\nread from the kmalloc-1k MFT record copy. The stack included\nntfs_lookup(), ntfs_iget(), ntfs_read_locked_inode(), ntfs_attr_name_get(),\nntfs_ucstonls(), and utf16s_to_utf8s().\n\nAdd a shared attribute value validator and use it before a lookup path\ncan return an attribute, including the AT_UNUSED enumeration case where\ncallers inspect returned attributes directly. The helper validates\nresident value bounds, minimum resident value sizes, variable-length\n$FILE_NAME fields, and non-resident mapping-pairs metadata that was\npreviously checked separately in both lookup paths.\n\nThis also preserves the intended resident @val matching semantics in the\nexternal attribute lookup path. The old duplicated validation block\noverwrote the actual resident value length with the type-specific minimum\nlength before comparing @val, so variable-length resident values could\nfail to match even when the bytes were identical. Keep the comparison on\nthe actual value length, and make ntfs_attrlist_entry_add() compare\nresident attributes with lowest_vcn zero instead of reading the\nnon-resident union member after a successful resident match.\n\nReject non-resident $FILE_NAME records too: the format requires\n$FILE_NAME to be resident and callers treat returned records as resident."}],"metrics":[{"cvssV3_1":{"baseScore":9.8,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:N - NTFS registers ntfs_export_ops; remote nfsd/ksmbd VFS lookups on an exported crafted NTFS volume reach ntfs_lookup→ntfs_iget→ntfs_read_locked_inode→ntfs_attr_name_get without local syscall access.\nAC:L - The attacker fully controls on-disk $FILE_NAME metadata (small resident value_length with large file_name_length) in a crafted image; the fix commit reproduced the slab OOB read via ntfs_lookup deterministically with no races.\nPR:N - Triggering needs only read access to mounted NTFS content (e.g., authenticated or guest NFS/SMB client on an exported share) or supplying removable media later mounted by the host; no init-namespace root or CAP_SYS_ADMIN on the lookup path.\nUI:N - Once a crafted NTFS volume is mounted and exported (or loop-mounted in a user namespace), normal remote lookups/opens reach the vulnerable attribute parsing without further victim clicks or cooperative actions.\nS:U - The slab out-of-bounds read and potential kernel crash stay within the mounting host kernel authority; this is standard filesystem parsing exploitation, not a VM escape, IOMMU bypass, or cross-sandbox scope change.\nC:H - Callers trust inflated file_name_length and ntfs_ucstonls/utf16s_to_utf8s read past the resident $FILE_NAME value in the kmalloc-1k MFT record copy, disclosing adjacent slab heap memory beyond a few bytes.\nI:H - Attacker-controlled file_name_length drives kernel parsing of forged resident metadata and adjacent slab contents; per kernel CNA guidance, this memory-corruption class can be leveraged for arbitrary kernel modification or control-flow hijack beyond the immediate read.\nA:H - KASAN reports slab-out-of-bounds read from the MFT record copy on lookup; reading past the resident $FILE_NAME value can oops or panic the kernel when accessing invalid adjacent memory."}]}],"providerMetadata":{"dateUpdated":"2026-08-17T05:41:36.117Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56"},{"url":"https://git.kernel.org/stable/c/d5803e3345dae9c6470bb61869885236276b9a35"}],"title":"ntfs: validate attribute values on lookup","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-72209","datePublished":"2026-08-15T05:54:04.772Z","dateReserved":"2026-08-09T03:40:39.912Z","dateUpdated":"2026-08-17T05:41:36.117Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:21:39","lastModifiedDate":"2026-08-17 06:18:21","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"72209","Ordinal":"1","Title":"ntfs: validate attribute values on lookup","CVE":"CVE-2026-72209","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"72209","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: validate attribute values on lookup\n\nntfs_attr_find() and ntfs_external_attr_find() check that generic\nresident attribute values fit in their attribute records and that\nfixed-size resident values are large enough. For variable-length resident\nformats, however, the fixed part is not enough: embedded length fields\ncan still point callers past the resident value.\n\nA crafted image can set a small resident $FILE_NAME value_length while\nleaving file_name_length large. Callers then trust file_name_length and\nread past the resident value when converting or comparing the name. This\nwas reproduced with a crafted image under KASAN as a slab-out-of-bounds\nread from the kmalloc-1k MFT record copy. The stack included\nntfs_lookup(), ntfs_iget(), ntfs_read_locked_inode(), ntfs_attr_name_get(),\nntfs_ucstonls(), and utf16s_to_utf8s().\n\nAdd a shared attribute value validator and use it before a lookup path\ncan return an attribute, including the AT_UNUSED enumeration case where\ncallers inspect returned attributes directly. The helper validates\nresident value bounds, minimum resident value sizes, variable-length\n$FILE_NAME fields, and non-resident mapping-pairs metadata that was\npreviously checked separately in both lookup paths.\n\nThis also preserves the intended resident @val matching semantics in the\nexternal attribute lookup path. The old duplicated validation block\noverwrote the actual resident value length with the type-specific minimum\nlength before comparing @val, so variable-length resident values could\nfail to match even when the bytes were identical. Keep the comparison on\nthe actual value length, and make ntfs_attrlist_entry_add() compare\nresident attributes with lowest_vcn zero instead of reading the\nnon-resident union member after a successful resident match.\n\nReject non-resident $FILE_NAME records too: the format requires\n$FILE_NAME to be resident and callers treat returned records as resident.","Type":"Description","Title":"ntfs: validate attribute values on lookup"}]}}}