CVE-2025-68369

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Jul 31, 2026
No patch confirmed yet.
generic

ntfs3: init run lock for extend inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be99c62ac7e7af514e4b13f83c891a3cccefaa48
generic

ntfs3: init run lock for extend inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ab5e8ebeee1caa4fcf8be7d8d62c0a7165469076
generic

ntfs3: init run lock for extend inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/907bf69c6b6ce5d038eec7a599d67b45b62624bc
generic

ntfs3: init run lock for extend inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79c8a77b1782e2ace96d063be3c41ba540d1e20a
generic

ntfs3: init run lock for extend inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e17555728bc469d484c59db4a0abc65c19bc315
generic

ntfs3: init run lock for extend inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/433d1f7c628c3cbdd7efce064d6c7acd072cf6c4
generic

ntfs3: init run lock for extend inode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19164d8228317f3f1fe2662a9ba587cfe3b2d29e

Vendor Advisories for CVE-2025-68369(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)6.1.162-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)6.1.162-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.9-1 (85 versions)6.17.13-1

All Vendor Advisories

(19)

Data Freshness Timeline

(refreshed 4× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 190 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:30 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-15 03:10 UTCEPSS rescore
  6. 2026-09-14 05:50 UTCOSV refresh
  7. 2026-09-13 16:46 UTCEPSS rescore
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-11 09:36 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-26 14:45 UTCEPSS rescore
  22. 2026-08-26 07:13 UTCOSV refresh
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-24 14:16 UTCEPSS rescore
  25. 2026-08-23 00:18 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:48 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:46 UTCEPSS rescore
  6. 2026-08-16 14:55 UTCEPSS rescore
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-11 13:42 UTCEPSS rescore
  12. 2026-08-10 23:59 UTCEPSS rescore
  13. 2026-08-09 22:53 UTCEG score recompute
  14. 2026-08-09 22:53 UTCVendor advisory
  15. 2026-08-09 22:53 UTCGHSA enrichment
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-08 16:36 UTCEPSS rescore
  18. 2026-08-08 05:29 UTCEG score recompute
  19. 2026-08-08 05:29 UTCVendor advisory
  20. 2026-08-08 05:29 UTCGHSA enrichment
  21. 2026-08-07 16:27 UTCEPSS rescore
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-06 07:16 UTCEG score recompute
  24. 2026-08-06 07:16 UTCVendor advisory
  25. 2026-08-06 07:15 UTCGHSA enrichment
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 12:48 UTCEG score recompute
  28. 2026-08-05 12:48 UTCVendor advisory
  29. 2026-08-05 12:47 UTCGHSA enrichment
  30. 2026-08-04 10:37 UTCEPSS rescore
  31. 2026-08-03 10:35 UTCEPSS rescore
  32. 2026-08-02 02:26 UTCEPSS rescore
  33. 2026-08-01 04:15 UTCEPSS rescore
  34. 2026-07-30 16:27 UTCEPSS rescore
  35. 2026-07-30 06:45 UTCEG score recompute
  36. 2026-07-30 06:45 UTCGHSA enrichment
  37. 2026-07-30 06:21 UTCEG score recompute 7.50
  38. 2026-07-30 06:21 UTCGHSA enrichment
  39. 2026-07-30 06:18 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  40. 2026-07-30 01:30 UTCEPSS rescore
  41. 2026-07-27 14:13 UTCEPSS rescore
  42. 2026-07-27 04:09 UTCOSV refresh
  43. 2026-07-26 14:54 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-25 14:17 UTCEPSS rescore
  46. 2026-07-25 14:17 UTCEPSS rescore
  47. 2026-07-24 14:17 UTCEPSS rescore
  48. 2026-07-23 14:18 UTCEPSS rescore
  49. 2026-07-23 14:18 UTCEPSS rescore
  50. 2026-07-23 03:02 UTCEG score recompute
  51. 2026-07-22 14:08 UTCEPSS rescore
  52. 2026-07-21 15:24 UTCEPSS rescore
  53. 2026-07-20 17:08 UTCEPSS rescore
  54. 2026-07-19 14:30 UTCEPSS rescore
  55. 2026-07-19 14:30 UTCEPSS rescore
  56. 2026-07-19 02:28 UTCEPSS rescore
  57. 2026-07-19 02:28 UTCEPSS rescore
  58. 2026-07-18 10:04 UTCEPSS rescore
  59. 2026-07-18 10:04 UTCEPSS rescore
  60. 2026-07-16 17:02 UTCEPSS rescore
  61. 2026-07-16 17:02 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-15 01:59 UTCEPSS rescore
  66. 2026-07-13 06:12 UTCEPSS rescore
  67. 2026-07-12 05:46 UTCEPSS rescore
  68. 2026-07-12 05:46 UTCEPSS rescore
  69. 2026-07-11 08:27 UTCEPSS rescore
  70. 2026-07-11 08:27 UTCEPSS rescore
  71. 2026-07-09 22:45 UTCOSV refresh
  72. 2026-07-09 19:10 UTCEPSS rescore
  73. 2026-07-08 15:15 UTCEPSS rescore
  74. 2026-07-07 13:46 UTCEPSS rescore
  75. 2026-07-06 16:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-68369?
CVE-2025-68369 is a high vulnerability published on December 24, 2025. 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.…
When was CVE-2025-68369 disclosed?
CVE-2025-68369 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68369 actively exploited?
CVE-2025-68369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.3% of all scored CVEs.
What is the CVSS score of CVE-2025-68369?
CVE-2025-68369 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-68369?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68369, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68369

Explore →

Is Your Infrastructure Affected by CVE-2025-68369?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.