Your message dated Sat, 15 Mar 2025 08:54:29 +0100 with message-id <[email protected]> has caused the report #1100470, regarding grub2-common: Segfault messages when running update-grub to be marked as having been forwarded to the upstream software author(s) The development of GRUB 2 <[email protected]>
(NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1100470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100470 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Hi, on Debian we got a bug report with a segfault in grub-mount when we added the CVE fixes to it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100470 It crashes on all 3 Windows NTFS Partitions with this: Program received signal SIGSEGV, Segmentation fault. Download failed: Invalid argument. Continuing without source file ./obj/grub-pc/../../grub-core/fs/ntfs.c. 0x000055555557de34 in find_attr (at=at@entry=0x555555694ea0, attr=attr@entry=128 '\200') at ../../grub-core/fs/ntfs.c:390 warning: 390 ../../grub-core/fs/ntfs.c: No such file or directory Line 390 is the same AFAICS on upstream grub.git and Debian packaging: while (at->attr_cur < mft_end && *at->attr_cur != 0xFF) I don't know what is special on their NTFS partitions. I can't reproduce this with my own dual-boot system.
--- End Message ---
