CVE-2025-68369: ntfs3: init run lock for extend inode
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 19164d8228317f3f1fe2662a9ba587cfe3b2d29e, 433d1f7c628c3cbdd7efce064d6c7acd072cf6c4, 5.15.198.
Low priority for now. Upgrade to Linux Linux 19164d8228317f3f1fe2662a9ba587cfe3b2d29e, 433d1f7c628c3cbdd7efce064d6c7acd072cf6c4, 5.15.198 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Dec 24, 2025
- Updated
- Oct 13, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.18affected
- 63eb6730ce0604d3eacf036c2f68ea70b068317c and later · before 79c8a77b1782e2ace96d063be3c41ba540d1e20aaffected · git
- 78d46f5276ed3589aaaa435580068c5b62efc921 and later · before 433d1f7c628c3cbdd7efce064d6c7acd072cf6c4affected · git
- 17249b2a65274f73ed68bcd1604e08a60fd8a278 and later · before 907bf69c6b6ce5d038eec7a599d67b45b62624bcaffected · git
- 37f65e68ba9852dc51c78dbb54a9881c3f0fe4f7 and later · before 6e17555728bc469d484c59db4a0abc65c19bc315affected · git
- 57534db1bbc4ca772393bb7d92e69d5e7b9051cf and later · before 19164d8228317f3f1fe2662a9ba587cfe3b2d29eaffected · git
- 4e8011ffec79717e5fdac43a7e79faf811a384b7 and later · before ab5e8ebeee1caa4fcf8be7d8d62c0a7165469076affected · git
- 4e8011ffec79717e5fdac43a7e79faf811a384b7 and later · before be99c62ac7e7af514e4b13f83c891a3cccefaa48affected · git
- 5.15.197 and later · before 5.15.198affected · semver
- 6.1.159 and later · before 6.1.160affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68367Dec 24, 2025 · macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse0Monitor
- ← EarlierCVE-2025-68368Dec 24, 2025 · md: init bioset in mddev_init0Monitor
- Later →CVE-2025-68370Dec 24, 2025 · coresight: tmc: add the handle of the event to the path31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 19164d8228317f3f1fe2662a9ba587cfe3b2d29e | Vendor (CNA) |
| Linux Linux | 433d1f7c628c3cbdd7efce064d6c7acd072cf6c4 | Vendor (CNA) |
| Linux Linux | 5.15.198 | Vendor (CNA) |
| Linux Linux | 6.1.160 | Vendor (CNA) |
| Linux Linux | 6.12.63 | Vendor (CNA) |
| Linux Linux | 6.17.13 | Vendor (CNA) |
| Linux Linux | 6.6.120 | Vendor (CNA) |
| Linux Linux | 6e17555728bc469d484c59db4a0abc65c19bc315 | Vendor (CNA) |
| Linux Linux | 79c8a77b1782e2ace96d063be3c41ba540d1e20a | Vendor (CNA) |
| Linux Linux | 907bf69c6b6ce5d038eec7a599d67b45b62624bc | Vendor (CNA) |
| Linux Linux | ab5e8ebeee1caa4fcf8be7d8d62c0a7165469076 | Vendor (CNA) |
| Linux Linux | be99c62ac7e7af514e4b13f83c891a3cccefaa48 | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/433d1f7c628c3cbdd7efce064d6c7acd072cf6c4
- git.kernel.org/stable/c/6e17555728bc469d484c59db4a0abc65c19bc315
- git.kernel.org/stable/c/79c8a77b1782e2ace96d063be3c41ba540d1e20a
- git.kernel.org/stable/c/907bf69c6b6ce5d038eec7a599d67b45b62624bc
- git.kernel.org/stable/c/ab5e8ebeee1caa4fcf8be7d8d62c0a7165469076
- git.kernel.org/stable/c/be99c62ac7e7af514e4b13f83c891a3cccefaa48
Vendor advisories and official records. Exploit/PoC links are deliberately left out.