CVE-2023-54063 json
fs/ntfs3: Fix OOB read in indx_insert_into_buffer
published 2025-12-24 10 mo ago modified 2026-08-05 3 mo ago also EUVD-2023-60263
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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().
Patch / fix
- Linux Linux 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4
- linux Debian 12 6.1.37-1
- linux Debian 14, Debian 13 6.3.7-1
debian advisories DEBIAN-CVE-2023-54063
- linux Ubuntu 22.04 LTS 5.15.0-79.86
- linux-aws Ubuntu 22.04 LTS 5.15.0-1042.47
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1039.47
- linux-gke Ubuntu 22.04 LTS 5.15.0-1039.44
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1035.38
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1039.44
- linux-azure Ubuntu 22.04 LTS 5.15.0-1045.52
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1025.30
ubuntu advisories UBUNTU-CVE-2023-54063
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/cd7e1d67924081717c5c96ead758a1a77867689a commit
- git.kernel.org/stable/c/17048287ac79abd33b275ac3b5738285d406481b commit
- git.kernel.org/stable/c/a7e5dba10ba1402dd6c2f961a70320770865c4a5 commit
- git.kernel.org/stable/c/4bf3b564e27a518f158a83d5e1a50064ed6136a0 commit
- git.kernel.org/stable/c/b8c44949044e5f7f864525fdffe8e95135ce9ce5 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-54063 updated cvss 7.8
kernel: Linux kernel: Out-of-bounds read in NTFS3 filesystem driver
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/cd7e1d67924081717c5c96ead758a1a77867689a
- git.kernel.org /stable/c/17048287ac79abd33b275ac3b5738285d406481b
- git.kernel.org /stable/c/a7e5dba10ba1402dd6c2f961a70320770865c4a5
- git.kernel.org /stable/c/4bf3b564e27a518f158a83d5e1a50064ed6136a0
- git.kernel.org /stable/c/b8c44949044e5f7f864525fdffe8e95135ce9ce5
Sources
- CVE List CVE-2023-54063
- NVD CVE-2023-54063
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.