linux: In the Linux kernel, the following vulnerability has been resolved: ntfs3: init run lock for extend inode After set...
CVE-2025-68369 is fixed in 23 products on 1 platform, first by DEBIAN-CVE-2025-68369, released December 24, 2025. It is not reported as exploited. Patch Radar priority: High.
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
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.12 · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| bpftool6.12-debuginfo · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel-livepatch-6.12.63-84.121 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12 · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-debuginfo · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-debuginfo-common-aarch64 · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-debuginfo-common-x86_64 · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-devel · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-headers · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-libbpf · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-libbpf-debuginfo · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-libbpf-devel · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-libbpf-static · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-modules-extra · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-modules-extra-common · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-tools · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-tools-debuginfo · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| kernel6.12-tools-devel · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| linux · Debian 12.15 (bookworm) | 6.1.162-1 | DEBIAN-CVE-2025-68369 | Dec 24, 2025 |
| linux · Debian 14 | 6.17.13-1 | DEBIAN-CVE-2025-68369 | Dec 24, 2025 |
| perf6.12 · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| perf6.12-debuginfo · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| python3-perf6.12 · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
| python3-perf6.12-debuginfo · amzn 2023 | 1:6.12.63-84.121.amzn2023 | ALAS2023-2026-1430 | Feb 16, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.