Name
dpkg
Version
1.22.0
Type
library
Description
Package maintenance system from Debian
Licenses
GPL-2.0-or-later
PURL
-
CPE
cpe:2.3:*:*:dpkg:1.22.0:*:*:*:*:*:*:*
Other Versions#
Patches#
#
Title
Author
Resolve
1
Patch #1
Joe Slater <jslater@windriver.com>
2
Our pre/postinsts expect $D to be set when running in a
Alexander Kanavin <alex.kanavin@gmail.com>
3
dpkg-deb/build.c: Remove usage of --clamp-mtime in tar
=?UTF-8?q?An=C3=ADbal=20Lim=C3=B3n?= <anibal.limon@linux.intel.com>
4
Add support for riscv32 CPU
Khem Raj <raj.khem@gmail.com>
5
Patch #5
Constantin Musca <constantinx.musca@intel.com>
6
Patch #6
Ricardo Ribalda <ricardo@ribalda.com>
7
Patch #7
Unknown
8
Adapt to linux-wrs kernel version, which has character
Alexander Kanavin <alex.kanavin@gmail.com>
9
dpkg: Support muslx32 build
sweeaun <swee.aun.khor@intel.com>
10
add musleabi to known target tripets
Khem Raj <raj.khem@gmail.com>
11
Patch #11
Krishnanjanappa, Jagadeesh <jagadeesh.krishnanjanappa@caviumnetworks.com>
12
build.c: ignore return of 1 from tar -cf
Paul Eggleton <paul.eggleton@linux.microsoft.com>
13
The lutimes function doesn't work properly for all
Alexander Kanavin <alex.kanavin@gmail.com>
14
dpkg-deb: Fix cleanup for control member with restricted
Guillem Jover <guillem@debian.org>
CVE-2025-6297
Vulnerabilities#
Name
Analysis
Description
Exploitable
It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).
Patched
It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is
documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on
adversarial .deb packages or with well compressible files, placed
inside a directory with permissions not allowing removal by a non-root
user, this can end up in a DoS scenario due to causing disk quota
exhaustion or disk full conditions.