SECUFOCUSNOW
Home›CVE index›CVE-2025-68369
Review reviewHigh

CVE-2025-68369

Linux

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_s...

CVSS
7.5
EPSS
0.40%
32.3% percentile
CISA KEV
Not listed
Published
2025.12.24
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.40%
Technical severityCVSS 7.5

Vulnerability overview

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_s...

Affected product and versions

Product
Linux
Affected versions
>= 63eb6730ce0604d3eacf036c2f68ea70b068317c < 79c8a77b1782e2ace96d063be3c41ba540d1e20a, >= 78d46f5276ed3589aaaa435580068c5b62efc921 < 433d1f7c628c3cbdd7efce064d6c7acd072cf6c4, >= 17249b2a65274f73ed68bcd1604e08a60fd8a278 < 907bf69c6b6ce5d038eec7a599d67b45b62624bc, >= 37f65e68ba9852dc51c78dbb54a9881c3f0fe4f7 < 6e17555728bc469d484c59db4a0abc65c19bc315, >= 57534db1bbc4ca772393bb7d92e69d5e7b9051cf < 19164d8228317f3f1fe2662a9ba587cfe3b2d29e, >= 4e8011ffec79717e5fdac43a7e79faf811a384b7 < ab5e8ebeee1caa4fcf8be7d8d62c0a7165469076, >= 4e8011ffec79717e5fdac43a7e79faf811a384b7 < be99c62ac7e7af514e4b13f83c891a3cccefaa48, >= 5.15.197 < 5.15.198, >= 6.1.159 < 6.1.160, >= 6.6.117 < 6.6.120, >= 6.12.58 < 6.12.63, >= 6.17.8 < 6.17.13, >= 6.18
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE
Not available
CVE-2025-68369 — Linux | SECUFOCUS NOW