CVE-2025-68369: Linux kernel · ntfs3: init run lock for extend inode
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 6.8.0-1059.65~22.04.1 : patch Linux kernel soon.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1059.65~22.04.1, 6.8.0-1054.57~22.04.1, 6.8.0-1052.55~22.04.1 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| linux-hwe-edge | Affected
| Fixed in
|
AI-suggested
A patch has been applied to initialize the run_lock when loading $Extend, resolving the vulnerability. Users should update to the Linux kernel version that includes this fix (commit 4e8011ffec79 or later). Patch status is confirmed by the vendor fix referenced in the description.
Description
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 do_truncate() routine, causing the run_lock uninitialized error reported by syzbot. Prior to patch 4e8011ffec79, if the inode mode of $Extend was not set to a regular file, the do_truncate() routine would not be entered. Add the run_lock initialization when loading $Extend. syzbot reported: INFO: trying to register non-static key. Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 assign_lock_key+0x133/0x150 kernel/locking/lockdep.c:984 register_lock_class+0x105/0x320 kernel/locking/lockdep.c:1299 __lock_acquire+0x99/0xd20 kernel/locking/lockdep.c:5112 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 down_write+0x96/0x1f0 kernel/locking/rwsem.c:1590 ntfs_set_size+0x140/0x200 fs/ntfs3/inode.c:860 ntfs_extend+0x1d9/0x970 fs/ntfs3/file.c:387 ntfs_setattr+0x2e8/0xbe0 fs/ntfs3/file.c:808
References
- nvd.nist.gov/vuln/detail/CVE-2025-68369 (opens in a new tab)
- git.kernel.org/stable/c/19164d8228317f3f1fe2662a9ba587cfe3b2d29e (opens in a new tab)
- git.kernel.org/stable/c/433d1f7c628c3cbdd7efce064d6c7acd072cf6c4 (opens in a new tab)
- git.kernel.org/stable/c/6e17555728bc469d484c59db4a0abc65c19bc315 (opens in a new tab)
- git.kernel.org/stable/c/79c8a77b1782e2ace96d063be3c41ba540d1e20a (opens in a new tab)
- git.kernel.org/stable/c/907bf69c6b6ce5d038eec7a599d67b45b62624bc (opens in a new tab)
- git.kernel.org/stable/c/ab5e8ebeee1caa4fcf8be7d8d62c0a7165469076 (opens in a new tab)
- git.kernel.org/stable/c/be99c62ac7e7af514e4b13f83c891a3cccefaa48 (opens in a new tab)
- ubuntu.com/security/CVE-2025-68369 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-68369 (opens in a new tab)
- ubuntu.com/security/notices/USN-8094-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8094-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8094-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8094-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8094-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-8152-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8179-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8184-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8179-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8185-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8179-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8203-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8204-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8185-2 (opens in a new tab)