fs/ntfs3: Fix OOB read in indx_insert_into_buffer
Summary
| CVE | CVE-2023-54063 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-12-24 13:16:08 UTC |
| Updated | 2026-08-04 10:19:26 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix OOB read in indx_insert_into_buffer Syzbot reported a OOB read bug: BUG: KASAN: slab-out-of-bounds in indx_insert_into_buffer+0xaa3/0x13b0 fs/ntfs3/index.c:1755 Read of size 17168 at addr ffff8880255e06c0 by task syz-executor308/3630 Call Trace: <TASK> memmove+0x25/0x60 mm/kasan/shadow.c:54 indx_insert_into_buffer+0xaa3/0x13b0 fs/ntfs3/index.c:1755 indx_insert_entry+0x446/0x6b0 fs/ntfs3/index.c:1863 ntfs_create_inode+0x1d3f/0x35c0 fs/ntfs3/inode.c:1548 ntfs_create+0x3e/0x60 fs/ntfs3/namei.c:100 lookup_open fs/namei.c:3413 [inline] If the member struct INDEX_BUFFER *index of struct indx_node is incorrect, that is, the value of __le32 used is greater than the value of __le32 total in struct INDEX_HDR. Therefore, OOB read occurs when memmove is called in indx_insert_into_buffer(). Fix this by adding a check in hdr_find_e(). |
Risk And Classification
Primary CVSS: v3.1 7.8 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.001700000 probability, percentile 0.066130000 (date 2026-08-06)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 82cae269cfa953032fbb8980a7d554d60fb00b17 cd7e1d67924081717c5c96ead758a1a77867689a git | Not specified |
| CNA | Linux | Linux | affected 82cae269cfa953032fbb8980a7d554d60fb00b17 17048287ac79abd33b275ac3b5738285d406481b git | Not specified |
| CNA | Linux | Linux | affected 82cae269cfa953032fbb8980a7d554d60fb00b17 a7e5dba10ba1402dd6c2f961a70320770865c4a5 git | Not specified |
| CNA | Linux | Linux | affected 82cae269cfa953032fbb8980a7d554d60fb00b17 4bf3b564e27a518f158a83d5e1a50064ed6136a0 git | Not specified |
| CNA | Linux | Linux | affected 82cae269cfa953032fbb8980a7d554d60fb00b17 b8c44949044e5f7f864525fdffe8e95135ce9ce5 git | Not specified |
| CNA | Linux | Linux | affected 5.15 | Not specified |
| CNA | Linux | Linux | unaffected 5.15 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.111 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.28 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.2.15 6.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.3.2 6.3.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.4 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/a7e5dba10ba1402dd6c2f961a70320770865c4a5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b8c44949044e5f7f864525fdffe8e95135ce9ce5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4bf3b564e27a518f158a83d5e1a50064ed6136a0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/cd7e1d67924081717c5c96ead758a1a77867689a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/17048287ac79abd33b275ac3b5738285d406481b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.