CVE-2025-68369: ntfs3: init run lock for extend inode

Published Dec 24, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ntfs3: init run lock for extend inode

After setting the inode mode of $Extend to a regular file, executing the truncate system call will enter the dotruncate() routine, causing the runlock uninitialized error reported by syzbot.

Prior to patch 4e8011ffec79, if the inode mode of $Extend was not set to a regular file, the dotruncate() routine would not be entered.

Add the runlock initialization when loading $Extend.

syzbot reported: INFO: trying to register non-static key. Call Trace: dumpstacklvl+0x189/0x250 lib/dumpstack.c:120 assignlockkey+0x133/0x150 kernel/locking/lockdep.c:984 registerlockclass+0x105/0x320 kernel/locking/lockdep.c:1299 lockacquire+0x99/0xd20 kernel/locking/lockdep.c:5112 lockacquire+0x120/0x360 kernel/locking/lockdep.c:5868 downwrite+0x96/0x1f0 kernel/locking/rwsem.c:1590 ntfssetsize+0x140/0x200 fs/ntfs3/inode.c:860 ntfsextend+0x1d9/0x970 fs/ntfs3/file.c:387 ntfssetattr+0x2e8/0xbe0 fs/ntfs3/file.c:808

Affected Software

2 affected componentsFixes available
Linux Linux kernel<4e8011ffec79
debian/linux
6.1.176-16.1.190-16.12.107-16.12.116-17.2.15-17.3.4-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.116-1Fixed in 7.2.15-1Fixed in 7.3.4-1
  2. Configuration

    Initialize run_lock when loading the $Extend inode to prevent the uninitialized-lock error during truncate operations.

    Linux ntfs3 run_lock = initialized

Event History

Dec 24, 2025
CVE Published
via MITRE·10:32 AM
Data Sourced
via MITRE·10:32 AM
DescriptionSeverity
Data Sourced
via NVD·11:16 AM
DescriptionSeverity

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2025-68369?

CVE-2025-68369 is considered a high-severity vulnerability due to its potential to cause system instability.

2

How do I fix CVE-2025-68369?

To fix CVE-2025-68369, you need to update the Linux kernel to a version that includes the patch for this vulnerability.

3

What software is affected by CVE-2025-68369?

CVE-2025-68369 affects the Linux kernel versions prior to 4e8011ffec79.

4

What type of vulnerability is CVE-2025-68369?

CVE-2025-68369 is an uninitialized memory access vulnerability in the Linux kernel's NTFS3 file system implementation.

5

What are the potential impacts of CVE-2025-68369?

The potential impacts of CVE-2025-68369 include system crashes and unintended behavior when truncating files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203