Package: e2fsprogs Version: 1.46.2-1 Severity: normal File: /usr/bin/lsattr
Hi, while debugging aide, I have stumbled upon a possible bug in lsattr or one of the underlying libraries. Doing lsattr on /dev/dri/card0 results in an abort with "stack smashing detected": | root@testsid85:~# sudo lsattr /dev/dri/card0 | *** stack smashing detected ***: terminated | Aborted Similiar behavior is observed when aide is trying to read the ext2 attrs of this file, so this is most probably a library issue. I can provide a backtrace if it helps. Greetings Marc -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/2 CPU threads) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages e2fsprogs depends on: ii libblkid1 2.36.1-7 ii libc6 2.31-11 ii libcom-err2 1.46.2-1 ii libext2fs2 1.46.2-1 ii libss2 1.46.2-1 ii libuuid1 2.36.1-7 ii logsave 1.46.2-1 Versions of packages e2fsprogs recommends: pn e2fsprogs-l10n <none> Versions of packages e2fsprogs suggests: pn e2fsck-static <none> pn fuse2fs <none> pn gpart <none> ii parted 3.4-1 -- no debconf information
