fs/ntfs3: bound page_lcns[] index by the log record
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound page_lcns[] index by the log record The copy_lcns loop and the redo shorten loop index page_lcns[] at j + i, where i runs up to the log record's lcns_follow. That count is checked only against the record's own length, not the target entry, so check_dp_table() (which validates the entry's lcns_follow) does not cover it: the copy_lcns entry may even be freshly allocated after that check, and find_dp() bounds j but not i. A crafted record thus overflows page_lcns[] of an otherwise valid entry. Add dp_range_ok() and reject, before each loop, any record whose run does not fit the entry. These are the only two page_lcns[] accesses indexed by the record rather than the entry, so together with the entry validation every access is now bounded. [almaz.alexandrovich@paragon-software.com: original patch contained changes to the problem already handled, applied partly]
- 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-89615
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 17:09 UTC · Revision 1
Source evidence
fs/ntfs3: bound page_lcns[] index by the log record
core-osv · Original sourcePublished 11 Sept 2026, 19:45 UTC
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound page_lcns[] index by the log record The copy_lcns loop and the redo shorten loop index page_lcns[] at j + i, where i runs up to the log record's lcns_follow. That count is checked only against the record's own length, not the target entry, so check_dp_table() (which validates the entry's lcns_follow) does not cover it: the copy_lcns entry may even be freshly allocated after that check, and find_dp() bounds j but not i. A crafted record thus overflows page_lcns[] of an otherwise valid entry. Add dp_range_ok() and reject, before each loop, any record whose run does not fit the entry. These are the only two page_lcns[] accesses indexed by the record rather than the entry, so together with the entry validation every access is now bounded. [almaz.alexandrovich@paragon-software.com: original patch contained changes to the problem already handled, applied partly]
osv:CVE-2026-89615
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": "7ab5254aecc26a8717182fb7365d77bf65a099ac818ab97b84ab9b25c837f5ae",
"url": "https://osv.dev/vulnerability/CVE-2026-89615",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "fs/ntfs3: bound page_lcns[] index by the log record",
"summary": "In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound page_lcns[] index by the log record The copy_lcns loop and the redo shorten loop index page_lcns[] at j + i, where i runs up to the log record's lcns_follow. That count is checked only against the record's own length, not the target entry, so check_dp_table() (which validates the entry's lcns_follow) does not cover it: the copy_lcns entry may even be freshly allocated after that check, and find_dp() bounds j but not i. A crafted record thus overflows page_lcns[] of an otherwise valid entry. Add dp_range_ok() and reject, before each loop, any record whose run does not fit the entry. These are the only two page_lcns[] accesses indexed by the record rather than the entry, so together with the entry validation every access is now bounded. [almaz.alexandrovich@paragon-software.com: original patch contained changes to the problem already handled, applied partly]",
"evidence": "osv:CVE-2026-89615",
"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-89615",
"aliases": [
"CVE-2026-89615"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:N/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": "31fdd11f75da9823500168cecb07aa45130915a3"
},
{
"fixed": "bb742d1030864c0fe140666f639428ba4e90b2ca"
},
{
"fixed": "61ca8cbbf68f77f25b699ed4358bd232f94ed43b"
},
{
"fixed": "f4c1bc6d7331f344ffcea93c2a37badcbe15baa6"
},
{
"fixed": "7ccb94901f38a062034b56b43c774050b113758f"
},
{
"fixed": "1135ebc225996b3ac1a295652b19a0a706737a6c"
},
{
"fixed": "6f7b9dbdc1b7520206abce0049bdd143eb536e75"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89615.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-89615.json"
}
}
],
"modified": "2026-10-28T02:30:51.139462332Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1135ebc225996b3ac1a295652b19a0a706737a6c",
"https://git.kernel.org/stable/c/31fdd11f75da9823500168cecb07aa45130915a3",
"https://git.kernel.org/stable/c/61ca8cbbf68f77f25b699ed4358bd232f94ed43b",
"https://git.kernel.org/stable/c/6f7b9dbdc1b7520206abce0049bdd143eb536e75",
"https://git.kernel.org/stable/c/7ccb94901f38a062034b56b43c774050b113758f",
"https://git.kernel.org/stable/c/bb742d1030864c0fe140666f639428ba4e90b2ca",
"https://git.kernel.org/stable/c/f4c1bc6d7331f344ffcea93c2a37badcbe15baa6",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89615.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-89615",
"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-89615.json"
}
},
"related_cves": [
{
"value": "CVE-2026-89615",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 519949,
"published_at": "2026-09-11T19:45:15.397+00:00"
}