fs/ntfs3: validate dirty page table on log replay
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate dirty page table on log replay Each DIR_PAGE_ENTRY ends in a page_lcns[] array whose length is the on-disk lcns_follow field. check_rstbl() validates the table bookkeeping but never checks that this array fits in the entry, so a crafted lcns_follow lets the v0->v1 conversion memmove and later replay passes run off the entry. Add check_dp_table() to reject, right after check_rstbl(), any entry larger than its size claims via struct_size() (the same expression used to allocate these entries, so the check is overflow-safe by construction). All consumers can then trust lcns_follow as the real capacity. This covers every page_lcns[] access whose index is bounded by the entry itself (the conversion memmove, the HotFix store via find_dp(), and the self-bounded scan loops). Accesses whose index comes from the log record need a separate bound and are handled in a follow-up patch.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.221, 6.1.188, 6.12.109, 6.18.50, 6.6.157, 7.2.4
- CVEs
- CVE-2026-89617
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 11:20 UTC · Revision 1
Source evidence
fs/ntfs3: validate dirty page table on log replay
core-osv · Original sourcePublished 11 Sept 2026, 19:45 UTC
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate dirty page table on log replay Each DIR_PAGE_ENTRY ends in a page_lcns[] array whose length is the on-disk lcns_follow field. check_rstbl() validates the table bookkeeping but never checks that this array fits in the entry, so a crafted lcns_follow lets the v0->v1 conversion memmove and later replay passes run off the entry. Add check_dp_table() to reject, right after check_rstbl(), any entry larger than its size claims via struct_size() (the same expression used to allocate these entries, so the check is overflow-safe by construction). All consumers can then trust lcns_follow as the real capacity. This covers every page_lcns[] access whose index is bounded by the entry itself (the conversion memmove, the HotFix store via find_dp(), and the self-bounded scan loops). Accesses whose index comes from the log record need a separate bound and are handled in a follow-up patch.
osv:CVE-2026-89617
Kernel
Fixed versions: 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4
Complete source record
{
"id": "846ce9582047c16cbedd2dd01810bf518dd15a1f767b608ba6d4f6cd54da7df2",
"url": "https://osv.dev/vulnerability/CVE-2026-89617",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "fs/ntfs3: validate dirty page table on log replay",
"summary": "In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate dirty page table on log replay Each DIR_PAGE_ENTRY ends in a page_lcns[] array whose length is the on-disk lcns_follow field. check_rstbl() validates the table bookkeeping but never checks that this array fits in the entry, so a crafted lcns_follow lets the v0->v1 conversion memmove and later replay passes run off the entry. Add check_dp_table() to reject, right after check_rstbl(), any entry larger than its size claims via struct_size() (the same expression used to allocate these entries, so the check is overflow-safe by construction). All consumers can then trust lcns_follow as the real capacity. This covers every page_lcns[] access whose index is bounded by the entry itself (the conversion memmove, the HotFix store via find_dp(), and the self-bounded scan loops). Accesses whose index comes from the log record need a separate bound and are handled in a follow-up patch.",
"evidence": "osv:CVE-2026-89617",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.221",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.188",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.157",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.109",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.50",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-89617",
"aliases": [
"CVE-2026-89617"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "b46acd6a6a627d876898e1c84d3f84902264b445"
},
{
"fixed": "0e07ea2fc45a7b4757ef7bf1f692cc0180a08323"
},
{
"fixed": "1e90b1703ee1a04cd3e9e399353fc536f5f3ba10"
},
{
"fixed": "d23155634a4bc1183e761d5eb2c043b2e693cc98"
},
{
"fixed": "1200c2779c43b62656ccbb67df9468a7a9af2484"
},
{
"fixed": "2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56"
},
{
"fixed": "0908da07c23be4f94b99dfd9a94765525f0fe4bd"
},
{
"fixed": "006cb7713dec10368e699abc4367e5faa334c9a5"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89617.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.15.0"
},
{
"fixed": "5.15.221"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.188"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.157"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.109"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.50"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89617.json"
}
}
],
"modified": "2026-10-28T02:30:28.117869632Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/006cb7713dec10368e699abc4367e5faa334c9a5",
"https://git.kernel.org/stable/c/0908da07c23be4f94b99dfd9a94765525f0fe4bd",
"https://git.kernel.org/stable/c/0e07ea2fc45a7b4757ef7bf1f692cc0180a08323",
"https://git.kernel.org/stable/c/1200c2779c43b62656ccbb67df9468a7a9af2484",
"https://git.kernel.org/stable/c/1e90b1703ee1a04cd3e9e399353fc536f5f3ba10",
"https://git.kernel.org/stable/c/2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56",
"https://git.kernel.org/stable/c/d23155634a4bc1183e761d5eb2c043b2e693cc98",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89617.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-89617",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89617.json"
}
},
"related_cves": [
{
"value": "CVE-2026-89617",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 494910,
"published_at": "2026-09-11T19:45:16.737+00:00"
}