# CVE-2026-53029: linux: In the Linux kernel, the following vulnerability has been resolved:  fs/ntfs3: prevent uninitialized lcn caused by ze...

CVE-2026-53029 is fixed in linux on 1 platform by DEBIAN-CVE-2026-53029 (version 7.0.10-1), released June 25, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-53029
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0014
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Jun 24, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  fs/ntfs3: prevent uninitialized lcn caused by zero len  syzbot reported a uninit-value in ntfs_iomap_begin [1].  Since runs was not touched yet, run_lookup_entry() immediately fails and returns false, which makes the value of "*len" 0. Simultaneously, the new value and err value are also 0, causing the logic in attr_data_get_block_locked() to jump directly to ok, ultimately resulting in *lcn being triggered before it is set [1].  In ntfs_iomap_begin(), the check for a 0 value in clen is moved forward to before updating lcn to avoid this [1].  [1] BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825  ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825  iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110  Local variable lcn created at:  ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.0.10-1 | [DEBIAN-CVE-2026-53029](https://patchblox.com/security/data/fix/linux/debian-cve-2026-53029.md) | Jun 25, 2026 |

---

Data as of 2026-11-09T07:25:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

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.