Package: linux-image-7.0.12+kali-amd64
Version: 7.0.12-2kali1
Architecture: amd64
Reproducibility: intermittent during buffered writes to an NTFS3 filesystem

Kali's current kernel encounters a known NTFS3 7.0.x regression during ordinary buffered writes.

Installed packages:

linux-image-7.0.12+kali-amd64 7.0.12-2kali1 amd64
linux-headers-7.0.12+kali-amd64 7.0.12-2kali1 amd64
linux-image-amd64 7.0.12-2kali1 amd64

Running kernel:

7.0.12+kali-amd64

The affected filesystem is NTFS mounted with the in-kernel ntfs3 driver through a VeraCrypt/dm-crypt mapping:

/dev/mapper/veracrypt1 on /media/veracrypt1 type ntfs3
(rw,relatime,uid=1000,gid=1000,dmask=0077,fmask=0077,iocharset=utf8,prealloc)

At 2026-08-04 01:13:43, an ordinary Python buffered write triggered:

kernel BUG at fs/iomap/buffered-io.c:1061!
Oops: invalid opcode: 0000 [0000001] SMP NOPTI
CPU: 23 UID: 1000 PID: 162816 Comm: python
Tainted: P OE 7.0.12+kali-amd64 0000001 PREEMPT(lazy)
RIP: iomap_write_end+0x1b4/0x1c0

Call trace:

iomap_file_buffered_write+0x20f/0x420
ntfs_file_write_iter+0x8de/0xc70 [ntfs3]
vfs_write+0x25d/0x480
ksys_write+0x73/0xf0
do_syscall_64+0xcd/0x15f0

After the Oops, filesystem operations became blocked. Python remained in uninterruptible D state in vfs_rename and could not be terminated even with SIGKILL. Thunar also entered D state in iterate_dir. Recovery required a full reboot.

This matches the known upstream and Debian reports:

Kernel Bugzilla #221446:
https://bugzilla.kernel.org/show_bug.cgi?id=221446

Debian #1141137:
https://bugs.debian.org/1141137

Upstream NTFS3 patch:
"[PATCH] fs/ntfs3: reject an oversized resident attribute on the inline iomap path"
https://lkml.org/lkml/2026/7/9/2675

CachyOS report reproducing it on Linux 7.0.12:
https://github.com/CachyOS/distribution/issues/459

The proposed upstream patch prevents oversized resident data from reaching the one-page IOMAP_INLINE path and triggering the BUG_ON in iomap_write_end_inline(). This failure is known across several 7.0.x releases, while Kali still ships 7.0.12 as the current linux-image-amd64 kernel. Cyka blyat: an ordinary filesystem write should return an error, not Oops the kernel, strand processes permanently in D state, and force a reboot.

Please backport the upstream fix to Kali's 7.0.12 kernel package, move to a kernel version containing the fix, or disable CONFIG_NTFS3_FS until the regression is resolved. The present behavior risks interrupted writes and turns normal filesystem activity into a system-level failure.