I am uploading a NMU to DELAYED/10 in order to fix this.
diff -Nru abootimg-0.6/debian/changelog abootimg-0.6/debian/changelog
--- abootimg-0.6/debian/changelog 2023-10-03 19:35:06.000000000 +0200
+++ abootimg-0.6/debian/changelog 2023-10-03 19:25:11.000000000 +0200
@@ -1,3 +1,12 @@
+abootimg (0.6-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Move Homepage to GitHub (Closes: #974609)
+ * Convert to source format 3.0 (Closes: #1007468)
+ * Prevent unpacking initrd to '/' (Closes: #955037)
+
+ -- Bastian Germann <b...@debian.org> Tue, 03 Oct 2023 19:25:11 +0200
+
abootimg (0.6-1) unstable; urgency=low
* New upstream release
diff -Nru abootimg-0.6/debian/control abootimg-0.6/debian/control
--- abootimg-0.6/debian/control 2023-10-03 19:35:06.000000000 +0200
+++ abootimg-0.6/debian/control 2023-10-03 19:25:06.000000000 +0200
@@ -4,7 +4,7 @@
Maintainer: Heiko Stuebner <mm...@debian.org>
Build-Depends: debhelper (>= 7), cdbs (>= 0.4.49), libblkid-dev
Standards-Version: 3.9.2
-Homepage: http://gitorious.org/ac100/abootimg
+Homepage: https://github.com/ggrandou/abootimg
Package: abootimg
Architecture: any
@@ -17,4 +17,4 @@
The original mkbootimg from Android can only create these images
where abootimg can also extract and modify them.
Handling android boot images is necessary when bringing other
- operating systems to android devices.
\ Kein Zeilenumbruch am Dateiende.
+ operating systems to android devices.
diff -Nru
abootimg-0.6/debian/patches/0001-always-unpack-initrd-to-relative-paths.patch
abootimg-0.6/debian/patches/0001-always-unpack-initrd-to-relative-paths.patch
---
abootimg-0.6/debian/patches/0001-always-unpack-initrd-to-relative-paths.patch
1970-01-01 01:00:00.000000000 +0100
+++
abootimg-0.6/debian/patches/0001-always-unpack-initrd-to-relative-paths.patch
2023-10-03 19:25:11.000000000 +0200
@@ -0,0 +1,25 @@
+From: Andrey Skvortsov <andrej.skvort...@gmail.com>
+Date: Fri, 27 Mar 2020 11:40:21 +0300
+Subject: always unpack initrd to relative paths
+
+If cpio archive contains absolute filenames, files are unpacked
+relative to host root '/', not 'ramdisk' directory.
+If abootimg-unpack-initrd is run as root, that could break host system
+and make it unbootable by overwriting important system files.
+
+Signed-off-by: Andrey Skvortsov <andrej.skvort...@gmail.com>
+---
+ abootimg-unpack-initrd | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/abootimg-unpack-initrd b/abootimg-unpack-initrd
+index 987239c..0113f3a 100755
+--- a/unpack-initrd
++++ b/unpack-initrd
+@@ -16,5 +16,5 @@ fi
+
+ mkdir -p $ramdisk
+
+-zcat $initrd | ( cd $ramdisk; cpio -i )
++zcat $initrd | ( cd $ramdisk; cpio -i --no-absolute-filenames)
+
diff -Nru abootimg-0.6/debian/patches/series abootimg-0.6/debian/patches/series
--- abootimg-0.6/debian/patches/series 1970-01-01 01:00:00.000000000 +0100
+++ abootimg-0.6/debian/patches/series 2023-10-03 19:25:11.000000000 +0200
@@ -0,0 +1 @@
+0001-always-unpack-initrd-to-relative-paths.patch
diff -Nru abootimg-0.6/debian/source/format abootimg-0.6/debian/source/format
--- abootimg-0.6/debian/source/format 1970-01-01 01:00:00.000000000 +0100
+++ abootimg-0.6/debian/source/format 2023-10-03 19:25:11.000000000 +0200
@@ -0,0 +1 @@
+3.0 (quilt)
