{"api_version":"1","generated_at":"2026-09-14T05:28:25+00:00","cve":"CVE-2026-89617","urls":{"html":"https://cve.report/CVE-2026-89617","api":"https://cve.report/api/cve/CVE-2026-89617.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89617","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89617"},"summary":{"title":"fs/ntfs3: validate dirty page table on log replay","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: validate dirty page table on log replay\n\nEach DIR_PAGE_ENTRY ends in a page_lcns[] array whose length is the on-disk\nlcns_follow field. check_rstbl() validates the table bookkeeping but never\nchecks that this array fits in the entry, so a crafted lcns_follow lets the\nv0->v1 conversion memmove and later replay passes run off the entry.\n\nAdd check_dp_table() to reject, right after check_rstbl(), any entry larger\nthan its size claims via struct_size() (the same expression used to allocate\nthese entries, so the check is overflow-safe by construction). All consumers\ncan then trust lcns_follow as the real capacity. This covers every\npage_lcns[] access whose index is bounded by the entry itself (the\nconversion memmove, the HotFix store via find_dp(), and the self-bounded\nscan loops). Accesses whose index comes from the log record need a separate\nbound and are handled in a follow-up patch.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:19:46","updated_at":"2026-09-13 07:17:27"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/006cb7713dec10368e699abc4367e5faa334c9a5","name":"https://git.kernel.org/stable/c/006cb7713dec10368e699abc4367e5faa334c9a5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1200c2779c43b62656ccbb67df9468a7a9af2484","name":"https://git.kernel.org/stable/c/1200c2779c43b62656ccbb67df9468a7a9af2484","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56","name":"https://git.kernel.org/stable/c/2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0908da07c23be4f94b99dfd9a94765525f0fe4bd","name":"https://git.kernel.org/stable/c/0908da07c23be4f94b99dfd9a94765525f0fe4bd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89617","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89617","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b46acd6a6a627d876898e1c84d3f84902264b445 1200c2779c43b62656ccbb67df9468a7a9af2484 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b46acd6a6a627d876898e1c84d3f84902264b445 2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b46acd6a6a627d876898e1c84d3f84902264b445 0908da07c23be4f94b99dfd9a94765525f0fe4bd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b46acd6a6a627d876898e1c84d3f84902264b445 006cb7713dec10368e699abc4367e5faa334c9a5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.109 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"89617","cve":"CVE-2026-89617","epss":"0.001380000","percentile":"0.035030000","score_date":"2026-09-13","updated_at":"2026-09-14 00:18:01"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/ntfs3/fslog.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"1200c2779c43b62656ccbb67df9468a7a9af2484","status":"affected","version":"b46acd6a6a627d876898e1c84d3f84902264b445","versionType":"git"},{"lessThan":"2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56","status":"affected","version":"b46acd6a6a627d876898e1c84d3f84902264b445","versionType":"git"},{"lessThan":"0908da07c23be4f94b99dfd9a94765525f0fe4bd","status":"affected","version":"b46acd6a6a627d876898e1c84d3f84902264b445","versionType":"git"},{"lessThan":"006cb7713dec10368e699abc4367e5faa334c9a5","status":"affected","version":"b46acd6a6a627d876898e1c84d3f84902264b445","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/ntfs3/fslog.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.15"},{"lessThan":"5.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.109","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.109","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"5.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: validate dirty page table on log replay\n\nEach DIR_PAGE_ENTRY ends in a page_lcns[] array whose length is the on-disk\nlcns_follow field. check_rstbl() validates the table bookkeeping but never\nchecks that this array fits in the entry, so a crafted lcns_follow lets the\nv0->v1 conversion memmove and later replay passes run off the entry.\n\nAdd check_dp_table() to reject, right after check_rstbl(), any entry larger\nthan its size claims via struct_size() (the same expression used to allocate\nthese entries, so the check is overflow-safe by construction). All consumers\ncan then trust lcns_follow as the real capacity. This covers every\npage_lcns[] access whose index is bounded by the entry itself (the\nconversion memmove, the HotFix store via find_dp(), and the self-bounded\nscan loops). Accesses whose index comes from the log record need a separate\nbound and are handled in a follow-up patch."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - log_replay() is reached only from ntfs_fill_super via ntfs_loadlog_and_replay while mounting a local NTFS block device; the dirty-page table is parsed from on-disk $LogFile, not from ksmbd, nfsd, or any received-packet path.\nAC:L - The attacker fully controls DIR_PAGE_ENTRY.lcns_follow and the restart table in a crafted $LogFile, so a value larger than the entry size reliably drives the v0 conversion memmove, HotFix store, and lcns_follow-bounded scan loops off the entry with no race or uncontrollable layout.\nPR:L - Triggering log replay requires mounting the malicious NTFS image (CAP_SYS_ADMIN). Unprivileged users can cause that mount via user+mount namespaces, loop-backed images, or common desktop/Android helpers (udisks/gvfs/USB automount) without init-namespace root.\nUI:N - No separate victim action is required: the attacker mounts their own crafted NTFS image (or causes automount of media they supply) and log replay runs automatically in ntfs_fill_super before any further file access.\nS:U - Corruption is confined to kernel heap during NTFS journal replay in the same kernel security authority; it is a local privilege-escalation/memory-safety issue, not a VM, IOMMU, or sandbox escape.\nC:H - Crafted lcns_follow makes DeleteDirtyClusters, HotFix, and dirty-page scan loops read page_lcns[] far past the kmemdup'd DIR_PAGE_ENTRY, disclosing adjacent kernel heap; that OOB read plus heap corruption yields arbitrary disclosure primitives.\nI:H - HotFix writes attacker-controlled LCNs and DeleteDirtyClusters zeros page_lcns[j] for j < the forged lcns_follow, overflowing the restart-table heap object into neighboring kmalloc data and enabling arbitrary kernel writes or control-flow hijack.\nA:H - Out-of-bounds heap access during mount-time log replay corrupts slab metadata or adjacent objects, causing kernel oops/panic, and a huge lcns_follow can also hang the mount path in a multi-billion-iteration scan."}]}],"providerMetadata":{"dateUpdated":"2026-09-13T06:31:56.314Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/1200c2779c43b62656ccbb67df9468a7a9af2484"},{"url":"https://git.kernel.org/stable/c/2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56"},{"url":"https://git.kernel.org/stable/c/0908da07c23be4f94b99dfd9a94765525f0fe4bd"},{"url":"https://git.kernel.org/stable/c/006cb7713dec10368e699abc4367e5faa334c9a5"}],"title":"fs/ntfs3: validate dirty page table on log replay","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89617","datePublished":"2026-09-11T19:45:16.737Z","dateReserved":"2026-09-11T19:38:34.735Z","dateUpdated":"2026-09-13T06:31:56.314Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:19:46","lastModifiedDate":"2026-09-13 07:17:27","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89617","Ordinal":"1","Title":"fs/ntfs3: validate dirty page table on log replay","CVE":"CVE-2026-89617","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89617","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: validate dirty page table on log replay\n\nEach DIR_PAGE_ENTRY ends in a page_lcns[] array whose length is the on-disk\nlcns_follow field. check_rstbl() validates the table bookkeeping but never\nchecks that this array fits in the entry, so a crafted lcns_follow lets the\nv0->v1 conversion memmove and later replay passes run off the entry.\n\nAdd check_dp_table() to reject, right after check_rstbl(), any entry larger\nthan its size claims via struct_size() (the same expression used to allocate\nthese entries, so the check is overflow-safe by construction). All consumers\ncan then trust lcns_follow as the real capacity. This covers every\npage_lcns[] access whose index is bounded by the entry itself (the\nconversion memmove, the HotFix store via find_dp(), and the self-bounded\nscan loops). Accesses whose index comes from the log record need a separate\nbound and are handled in a follow-up patch.","Type":"Description","Title":"fs/ntfs3: validate dirty page table on log replay"}]}}}