linux: In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix memory leak if ntfs_read_mft faile...
CVE-2023-54077 is fixed in 20 products on 1 platform, first by ALAS2023-2023-184, released May 25, 2023. It is not reported as exploited. Patch Radar priority: High.
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix memory leak if ntfs_read_mft failed Label ATTR_ROOT in ntfs_read_mft() sets is_root = true and ni->ni_flags |= NI_FLAG_DIR, then next attr will goto label ATTR_ALLOC and alloc ni->dir.alloc_run. However two states are not always consistent and can make memory leak. 1) attr_name in ATTR_ROOT does not fit the condition it will set is_root = true but NI_FLAG_DIR is not set. 2) next attr_name in ATTR_ALLOC fits the condition and alloc ni->dir.alloc_run 3) in cleanup function ni_clear(), when NI_FLAG_DIR is set, it frees ni->dir.alloc_run, otherwise it frees ni->file.run 4) because NI_FLAG_DIR is not set in this case, ni->dir.alloc_run is leaked as kmemleak reported: unreferenced object 0xffff888003bc5480 (size 64): backtrace: [<000000003d42e6b0>] __kmalloc_node+0x4e/0x1c0 [<00000000d8e19b8a>] kvmalloc_node+0x39/0x1f0 [<00000000fc3eb5b8>] run_add_entry+0x18a/0xa40 [ntfs3] [<0000000011c9f978>] run_unpack+0x75d/0x8e0 [ntfs3] [<00000000e7cf1819>] run_unpack_ex+0xbc/0x500 [ntfs3] [<00000000bbf0a43d>] ntfs_iget5+0xb25/0x2dd0 [ntfs3] [<00000000a6e50693>] ntfs_fill_super+0x218d/0x3580 [ntfs3] [<00000000b9170608>] get_tree_bdev+0x3fb/0x710 [<000000004833798a>] vfs_get_tree+0x8e/0x280 [<000000006e20b8e6>] path_mount+0xf3c/0x1930 [<000000007bf15a5f>] do_mount+0xf3/0x110 ... Fix this by always setting is_root and NI_FLAG_DIR together.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| bpftool-debuginfo · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-debuginfo · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-debuginfo-common-aarch64 · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-debuginfo-common-x86_64 · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-devel · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-headers · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-libbpf · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-libbpf-devel · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-libbpf-static · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-livepatch-6.1.29-47.49 · amzn 2023 | 1.0-0.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-tools · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-tools-debuginfo · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| kernel-tools-devel · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| linux · Debian 12.15 (bookworm) | 6.1.37-1 | DEBIAN-CVE-2023-54077 | Dec 24, 2025 |
| linux · Debian 13.5 (trixie) | 6.3.7-1 | DEBIAN-CVE-2023-54077 | Dec 24, 2025 |
| linux · Debian 14 | 6.3.7-1 | DEBIAN-CVE-2023-54077 | Dec 24, 2025 |
| perf · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| perf-debuginfo · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| python3-perf · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
| python3-perf-debuginfo · amzn 2023 | 6.1.29-47.49.amzn2023 | ALAS2023-2023-184 | May 25, 2023 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.