dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53029

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 7.0.10 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel's NTFS3 driver, an uninitialized value bug exists in ntfs_iomap_begin() where the local variable lcn is read before being set. When run_lookup_entry() fails and returns false, *len becomes 0, causing the logic in attr_data_get_block_locked() to bypass proper initialization and jump directly to 'ok', resulting in the uninitialized lcn being used.

MitigationApply the kernel patch that moves the check for clen=0 before lcn is updated to prevent the uninitialized value from being used.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 7.0, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run 'uname -r' to get the running kernel version
    Affected if The version is >= 7.0 and < 7.0.10 (for example, 7.0.1 through 7.0.9)
  2. Verify NTFS3 driver is available
    Run 'modinfo ntfs3' or check if /sys/module/ntfs3 exists, or check /proc/filesystems for ntfs3
    Affected if The NTFS3 driver module is loaded or compiled into the kernel
  3. Check for NTFS partitions mounted with NTFS3
    Run 'mount | grep ntfs3' or check 'cat /proc/mounts' for ntfs3 mount entries
    Affected if Any NTFS partition is actively mounted using the ntfs3 driver

You are affected if your kernel version falls within 7.0 to 7.0.9 AND you have NTFS partitions mounted using the NTFS3 driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.10 or later
Fixed in 7.0.10
Interim mitigation

Apply the kernel patch that moves the check for clen=0 before lcn is updated to prevent the uninitialized value from being used.

Recommended fix High confidence

Linux Kernel 7.0.10 or later

  1. Identify the current Linux kernel version running on affected systems using 'uname -r'
  2. Schedule a maintenance window for the kernel upgrade
  3. Obtain Linux kernel 7.0.10 or later from official kernel.org sources or your distribution's kernel package repository
  4. Apply the kernel upgrade using your distribution's standard package manager or kernel installation procedure (e.g., 'apt-get install linux-image-7.0.10' or 'yum install kernel-7.0.10')
  5. Update bootloader configuration if necessary (GRUB, etc.)
  6. Reboot the system into the new kernel
  7. Verify the kernel version is 7.0.10 or later with 'uname -r' and confirm the ntfs3 module loads without errors
Caveat Kernel upgrades may introduce compatibility changes with drivers or modules; test thoroughly in non-production environments first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53029 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53029 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data