linux-kernel - Re: [PATCH] ntfs3: prevent operations on NTFS system files

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CADhLXY4CmHm7tP+M3RzS66tA3pqt_JghbaF6DRozZBjtpdCzEA@mail.gmail.com>
Date: Tue, 14 Oct 2025 21:31:29 +0530
From: Deepanshu Kartikey <kartikey406@...il.com>
To: almaz.alexandrovich@...agon-software.com, 
	penguin-kernel@...ove.sakura.ne.jp
Cc: ntfs3@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	syzbot+3e58a7dc1a8c00243999@...kaller.appspotmail.com
Subject: Re: [PATCH] ntfs3: prevent operations on NTFS system files

Hi Tetsuo,

You're absolutely right to question this. I made an error in my patch.

Looking at the debug logs again, the problematic inode is #25, which is
a file INSIDE the $Extend directory, not $Extend itself (which is inode 11).

My check `if (ni->mi.rno < MFT_REC_FREE)` only blocks inodes 0-15, so it
wouldn't actually block inode 25 at all. This means my additional check
doesn't solve the real problem.

Edward's simpler patch (just initializing run_lock for $Extend records)
is the correct minimal fix for this crash. I apologize for the confusion.

Thank you for catching this.

Best regards,
Deepanshu