{"api_version":"1","generated_at":"2026-06-25T15:48:42+00:00","cve":"CVE-2026-53029","urls":{"html":"https://cve.report/CVE-2026-53029","api":"https://cve.report/api/cve/CVE-2026-53029.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53029","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53029"},"summary":{"title":"fs/ntfs3: prevent uninitialized lcn caused by zero len","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: prevent uninitialized lcn caused by zero len\n\nsyzbot reported a uninit-value in ntfs_iomap_begin [1].\n\nSince runs was not touched yet, run_lookup_entry() immediately fails\nand returns false, which makes the value of \"*len\" 0.\nSimultaneously, the new value and err value are also 0, causing the\nlogic in attr_data_get_block_locked() to jump directly to ok, ultimately\nresulting in *lcn being triggered before it is set [1].\n\nIn ntfs_iomap_begin(), the check for a 0 value in clen is moved forward\nto before updating lcn to avoid this [1].\n\n[1]\nBUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110\n\nLocal variable lcn created at:\n ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-24 17:17:14","updated_at":"2026-06-24 17:17:14"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/e98266e823a1fa06fe6499df61aeaac2fd6f7a49","name":"https://git.kernel.org/stable/c/e98266e823a1fa06fe6499df61aeaac2fd6f7a49","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/485f750cac3d8bdf5552a0e3d79ce5e3a03ece49","name":"https://git.kernel.org/stable/c/485f750cac3d8bdf5552a0e3d79ce5e3a03ece49","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53029","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53029","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 10d7c95af043b45a85dc738c3271bf760ff3577e 485f750cac3d8bdf5552a0e3d79ce5e3a03ece49 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 10d7c95af043b45a85dc738c3271bf760ff3577e e98266e823a1fa06fe6499df61aeaac2fd6f7a49 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.10 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/ntfs3/inode.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"485f750cac3d8bdf5552a0e3d79ce5e3a03ece49","status":"affected","version":"10d7c95af043b45a85dc738c3271bf760ff3577e","versionType":"git"},{"lessThan":"e98266e823a1fa06fe6499df61aeaac2fd6f7a49","status":"affected","version":"10d7c95af043b45a85dc738c3271bf760ff3577e","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/ntfs3/inode.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.10","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.10","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: prevent uninitialized lcn caused by zero len\n\nsyzbot reported a uninit-value in ntfs_iomap_begin [1].\n\nSince runs was not touched yet, run_lookup_entry() immediately fails\nand returns false, which makes the value of \"*len\" 0.\nSimultaneously, the new value and err value are also 0, causing the\nlogic in attr_data_get_block_locked() to jump directly to ok, ultimately\nresulting in *lcn being triggered before it is set [1].\n\nIn ntfs_iomap_begin(), the check for a 0 value in clen is moved forward\nto before updating lcn to avoid this [1].\n\n[1]\nBUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110\n\nLocal variable lcn created at:\n ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786"}],"providerMetadata":{"dateUpdated":"2026-06-24T16:29:37.361Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/485f750cac3d8bdf5552a0e3d79ce5e3a03ece49"},{"url":"https://git.kernel.org/stable/c/e98266e823a1fa06fe6499df61aeaac2fd6f7a49"}],"title":"fs/ntfs3: prevent uninitialized lcn caused by zero len","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53029","datePublished":"2026-06-24T16:29:37.361Z","dateReserved":"2026-06-09T07:44:35.380Z","dateUpdated":"2026-06-24T16:29:37.361Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-24 17:17:14","lastModifiedDate":"2026-06-24 17:17:14","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53029","Ordinal":"1","Title":"fs/ntfs3: prevent uninitialized lcn caused by zero len","CVE":"CVE-2026-53029","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53029","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: prevent uninitialized lcn caused by zero len\n\nsyzbot reported a uninit-value in ntfs_iomap_begin [1].\n\nSince runs was not touched yet, run_lookup_entry() immediately fails\nand returns false, which makes the value of \"*len\" 0.\nSimultaneously, the new value and err value are also 0, causing the\nlogic in attr_data_get_block_locked() to jump directly to ok, ultimately\nresulting in *lcn being triggered before it is set [1].\n\nIn ntfs_iomap_begin(), the check for a 0 value in clen is moved forward\nto before updating lcn to avoid this [1].\n\n[1]\nBUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110\n\nLocal variable lcn created at:\n ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786","Type":"Description","Title":"fs/ntfs3: prevent uninitialized lcn caused by zero len"}]}}}